I'm not sure if this is the right place to submit this bug. If not please redirect me, thanks!
Issue:
Registry puller followed by a cluster reboot results in users not able to login.
Ocp version: 4.3.0-0.nightly-s390x-2020-05-04-145831 on s390x z/VM.
Steps to reproduce:
1. Use registry puller: https://github.com/knrc/registry-puller/ to set up custom operators on operatorhub.
2. Reboot all nodes
3. Watch as network,openshift-apiserver, and operator-lifecycle-manager-packageserver operators do no become available again.
oc login gets: "Error from server (InternalError): Internal error occurred: unexpected response: 503"
From system:admin serviceaccount running oc whoami gets "Error from server (ServiceUnavailable): the server is currently unable to handle the request (get users.user.openshift.io ~)"

I'm not sure how to debug this further, doing an "oc adm must-gather" gives:
[must-gather ] OUT the server is currently unable to handle the request (get imagestreams.image.openshift.io must-gather)
[must-gather ] OUT
[must-gather ] OUT Using must-gather plugin-in image: quay.io/openshift/origin-must-gather:latest
[must-gather ] OUT namespace/openshift-must-gather-fvcl8 created
[must-gather ] OUT clusterrolebinding.rbac.authorization.k8s.io/must-gather-9gtqq created
[must-gather ] OUT clusterrolebinding.rbac.authorization.k8s.io/must-gather-9gtqq deleted
[must-gather ] OUT namespace/openshift-must-gather-fvcl8 deleted
Error from server (Forbidden): pods "must-gather-" is forbidden: error looking up service account openshift-must-gather-fvcl8/default: serviceaccount "default" not found