May be dup as https://bugzilla.redhat.com/show_bug.cgi?id=1625194 with https://bugzilla.redhat.com/show_bug.cgi?id=1668632 as one of the whatever causes
Hi Xingxing Xia, The thing is the project status on the CLI is not showing as terminating but only on the "web console" unlike the BZ 1625194 where you can see the status on the CLI. on the oc get projects output , the project in quesion is not present.
Hi Paul, Thank you for the information. Unfortunately , that cluster is no longer available. But I will answer your questions. Q: can you confirm you were logged into oc as `kube:admin` or `system:admin` and definitely in the correct cluster? A: Yes I was logged in as the kube:admin , and the project was not there in.
We haven't been able to reproduce. There are several well-known issues around projects getting stuck in terminating like bug 1625194 and bug 1670994. The API server responded with "unable to create new content in namespace kojima because it is being terminated", which means that the project did in fact still exist (at least at the time the screenshot was taken). The console showing the project to the user in the console is likely correct. > Launch around 5-6 applications Note that there is an expected delay from when you delete the project until everything gets cleaned up and the project is removed from the list. Depending on how much later you checked using oc, it could be that the project had since been deleted. Since the cluster is gone and we can't reproduce, we've lost the chance to debug further. I'm going to close as insufficient data as this is likely a duplicate of an existing bug already. If you can reproduce, please reopen and 1. Double-check whether oc and web console show the same content for the projects list at the same time 2. Check `oc get clusteroperators` to determine whether one of the cluster operators is failing, which might cause projects to be stuck in terminating