Comment 3 for bug 1913039

many important k8s resources are not found on the impacted system, which is a VBox lab.
Basically there is no pods running. cert-manager and dc-cert namespaces don't exist.
sysinv try to look at the k8s secret before unlock, as the critical data isn't accessible, unlock is rejected.
This looks like a system level failure. As it is on a VBox, resources could be part of the issue (it is not identified).

controller-1:~$ kubectl get pods --all-namespaces
No resources found
controller-1:~$ kubectl get namespaces
NAME STATUS AGE
default Active 6h2m
kube-node-lease Active 6h2m
kube-public Active 6h2m
kube-system Active 6h2m

cert-manager application was applied
system application-list
+--------------------------+----------+-----------------------------------+------------------------------------+----------+-----------+
| application | version | manifest name | manifest file | status | progress |
+--------------------------+----------+-----------------------------------+------------------------------------+----------+-----------+
| cert-manager | 20.06-4 | cert-manager-manifest | certmanager-manifest.yaml | applied | completed |
| nginx-ingress-controller | 20.06-0 | nginx-ingress-controller-manifest | nginx_ingress_controller_manifest. | applied | completed |
| | | | yaml | | |
| | | | | | |
| oidc-auth-apps | 20.06-26 | oidc-auth-manifest | manifest.yaml | uploaded | completed |
| platform-integ-apps | 20.06-9 | platform-integration-manifest | manifest.yaml | uploaded | completed |
+--------------------------+----------+-----------------------------------+------------------------------------+----------+-----------+
[sysadmin@controller-1 ~(keystone_admin)]$