Bug 1879633

Summary:	(4.6) cluster operator authentication degraded on periodic-ci-openshift-release-master-ocp-4.6-e2e-aws-proxy
Product:	OpenShift Container Platform	Reporter:	Pratik Mahajan <pmahajan>
Component:	Cloud Compute	Assignee:	Alberto <agarcial>
Cloud Compute sub component:	Other Providers	QA Contact:	sunzhaohua <zhsun>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	low
Priority:	low	CC:	adahiya, aos-bugs, kgarriso, mfojtik, slaznick, wking
Version:	4.6
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:	operator install authentication
Last Closed:	2020-09-18 07:58:09 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 Pratik Mahajan 2020-09-16 17:07:15 UTC

test:
operator install authentication 

cluster operator authentication failing repeatedly citing multiple reasons on periodic-ci-openshift-release-master-ocp-4.6-e2e-aws-proxy

is failing frequently in CI, see search results:
https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=operator+install+authentication

Attaching few logs...
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.6-e2e-aws-proxy/1306202351639465984
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.6-e2e-aws-proxy/1306237263985774592
https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.6-e2e-aws-proxy/1306246450585276416

Comment 1 Abhinav Dahiya 2020-09-16 17:26:33 UTC

Moving to auth team to pin point why proxy is affecting their cluster.

Comment 2 Maru Newby 2020-09-16 18:57:27 UTC

Leaving open to discourage further bug filing by build watchers, but afiact this is non-actionable (failures are effectively exploded clusters with 11+ failed operator installs) and not caused by auth. Should likely be closed when groomed for the next sprint.

Comment 3 Standa Laznicka 2020-09-17 07:32:31 UTC

Actually, all of the clusters from the logs in the first comment share the same symptoms - there are no worker nodes, therefore the default router does not get scheduled, therefore the authn operator (and the others) go degraded. Not sure if MCO or installer team would be the right one to move this to, choosing the former.

Comment 4 Kirsten Garrison 2020-09-17 17:28:31 UTC

Missing worker nodes isn't MCO (and the MCO logs look fine) I'll pass to Machine API Operator to take a look and they can decide whether to keep or pass to installer.

Comment 5 Alberto 2020-09-18 07:58:09 UTC


*** This bug has been marked as a duplicate of bug 1875773 ***