Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2047846

Summary:	periodic-ci-openshift-release-master-ci-4.6-e2e-azure 401s cause terminal failure
Product:	OpenShift Container Platform	Reporter:	Scott Dodson <sdodson>
Component:	Cloud Compute	Assignee:	Joel Speed <jspeed>
Cloud Compute sub component:	Other Providers	QA Contact:	sunzhaohua <zhsun>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	sippy
Version:	4.6
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:	job=periodic-ci-openshift-release-master-ci-4.6-e2e-azure=all
Last Closed:	2022-02-24 13:42:00 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:
Bug Depends On:	2047845, 2051576, 2057559, 2057960
Bug Blocks:

Description Scott Dodson 2022-01-28 17:26:53 UTC

job:
periodic-ci-openshift-release-master-ci-4.6-e2e-azure 

is failing frequently in CI, see testgrid results:
https://testgrid.k8s.io/redhat-openshift-ocp-release-4.6-blocking#periodic-ci-openshift-release-master-ci-4.6-e2e-azure


These are failing due to lack of machines, debugging that it looks to be the same root cause as https://bugzilla.redhat.com/show_bug.cgi?id=2030488

We see 401s from machine api azure provider

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.6-e2e-azure/1486662970124537856/artifacts/e2e-azure/gather-extra/artifacts/machines.json

https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.6-e2e-azure/1486662970124537856

Comment 2 Joel Speed 2022-02-23 14:37:58 UTC

As this has already been backported through to 4.8, and this isn't a security fix, I'm hesitant to backport it any further.

@sdodson Do you believe this is important to backport further?

Comment 3 Scott Dodson 2022-02-23 15:39:55 UTC

(In reply to Joel Speed from comment #2)
> As this has already been backported through to 4.8, and this isn't a
> security fix, I'm hesitant to backport it any further.
> 
> @sdodson Do you believe this is important to backport further?

Since this causes installation to fail in CI and we lose signal everytime that happens lets go ahead and backport to all currently supported releases provided it's not challenging to do so.

Comment 5 Scott Dodson 2022-02-24 13:42:00 UTC


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