Description of problem: Authentication operator remains progressing with message: Cluster operator authentication Progressing is True with ProgressingWellKnownNotReady: Progressing: got '404 Not Found' status while trying to GET the OAuth well-known https://10.0.0.17:6443/.well-known/oauth-authorization-server endpoint data Version-Release number of selected component (if applicable): 4.3.0 Additional info: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-ocp-installer-e2e-openstack-serial-4.3/777 Possibly related to https://bugzilla.redhat.com/show_bug.cgi?id=1700046
Trying to get all nodes up took way too long, you're seeing this error because kube-apiservers weren't able to deploy to their latest version, which serves the .well-known endpoint, because of the nodes.
@Standa - I request that a separate bug be opened against Auth. If we need all nodes for the .well_known endpoint to be available, we should have a more useful/actionable error message. Example: ``` ProgressingWellKnownNotReady: Could not find the OAuth well-known endpoint. Please verify that all nodes in the cluster are available and the kube-apiserver is available. ```
That's fair Adam, please open that bug.
I don't know if there is a problem here that can be addressed. If a bug was opened with Auth, then I think figuring out the issue should be there. (I looked to verify Ryan's finding of the 'name is reserved' error appearing, and couldn't find indication it was). Thus, I'm closing as NOTABUG. Please re-open if you think there is some Node specific issue here.