Bug 1789658

Summary:	[openstack] Authentication operator progressing: 404 Not Found status while trying to GET the OAuth well-known
Product:	OpenShift Container Platform	Reporter:	Adam Kaplan <adam.kaplan>
Component:	Node	Assignee:	Peter Hunt <pehunt>
Status:	CLOSED NOTABUG	QA Contact:	Sunil Choudhary <schoudha>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.3.0	CC:	aos-bugs, gblomqui, jokerman, mfojtik, slaznick
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	buildcop
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-05 18:28:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Adam Kaplan 2020-01-10 02:40:47 UTC

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

Comment 1 Standa Laznicka 2020-01-10 09:30:23 UTC

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.

Comment 3 Adam Kaplan 2020-01-16 22:17:14 UTC

@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.

```

Comment 4 Standa Laznicka 2020-01-23 12:37:56 UTC

That's fair Adam, please open that bug.

Comment 5 Peter Hunt 2020-03-05 18:28:59 UTC

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.