workspace cannot be removed (Deleted projects will still be shown)
in progress
S
Sadegh Mohseni
After separating the corresponding building blocks, the workspace still cannot be removed.
After observing the workspace and projects, it was found that the deleted projects were still shown in the removal mask, even though they had already been deleted and were no longer visible in the project list.
This post was marked as
in progress
J
Julia Rengshausen
This problem even comes up if there was never a tenant in any of the projects in the workspace. You have to wait for a few minutes after deleting the project(s) until it is possible to delete the workspace. The error message does not give any further information.
Polina Sadykova
Merged in a post:
Deleting Workspace fails if tenant is marked for deletion
Felix
As long as at least one tenant is marked for deletion, workspace creation fails with an error.
When I as a admin inspect this, all projects are shown as deleted, so I think that meshStack is misbehaving.
Workaround: Confirm tenant deletion.
Expected behavior: Error message makes it clear that a tenant waits for deletion.
Polina Sadykova
Thank you a lot! We will keep you updated on the progress of resolving this issue.
Jelle den Burger
Thank you for letting us know. This seems indeed like a bug and we will work on resolving the issue.
Have you in the mean time been able to resolve the issue via a workaround or is the deletion still not possible?
S
Sadegh Mohseni
Jelle den Burger its still not possible to delete this and another workspace
F
Fabian Muscariello
Sadegh Mohseni It looks like there's still a tenant inside that project that requires manual deletion. So, the person who maintains the kubernetes platform must first delete that tenant manually, and then has to confirm in meshStack that it was deleted. They can do this inside the admin area at the section "Platforms" -> "Deleted Tenants" (see screenshot).
Can you check if you're able to delete the workspace after confirming that the tenant was deleted?
S
Sadegh Mohseni
Fabian Muscariello thank you for your response A corresponding error display makes life and detection of errors thousand times easier. A user without admin permissions can never do anything with such an error message and that is not a good UX journey. It would be great if the errors were also displayed accordingly.
F
Fabian Muscariello
Sadegh Mohseni Thank you for your feedback, we are tracking this as a bug so that users without admin access will have clear guidance on how to proceed in such cases.