Renaming project is only superficial, might lead to bricked state on `project down`

Open SteinRobert opened this issue 3 years ago • 1 comments

Moved from https://github.com/unikubehq/frontend/issues/367

I'm not sure whether this issue is correctly in the frontend, or whether the problem lies somewhere else.

I renamed a project in the frontend, which also appeared under unikube project commands with the new name (FF AH Keycloak). However when running unikiube project up, the cli tries to create a cluster with the old name/slug (FF Automation Hub Keycloak 2):

Jan 24 '22 16:01 SteinRobert

Update: I've just renamed a project ("FF AH Keycloak" to "FF AH"). I still had the k3d cluster named "unikube-ff-ah-keycloak", which was spun up by project up. However a project down for "FF AH" reports following error: [INFO] No Kubernetes cluster to stop for 'FF AH'

Now I'm kind of stuck, as unikube still lists "FF AH" as up, but can't shut it down.

Update2: I can't reproduce that behavior currently, it might've also been a side-effect from Telepresence not starting.

Jun 20 '22 09:06 tschale