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

Bug 1775646

Summary:	cluster-network-operator incorrectly marking as Degraded at install-time due to multus-admission-controller
Product:	OpenShift Container Platform	Reporter:	Casey Callendrello <cdc>
Component:	Networking	Assignee:	Ben Bennett <bbennett>
Networking sub component:	openshift-sdn	QA Contact:	Weibin Liang <weliang>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aconstan, weliang
Version:	4.3.0	Flags:	weliang: needinfo-
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-04 11:16:20 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 Casey Callendrello 2019-11-22 13:57:58 UTC

Because the multus-admission-controller needs the service-ca-controller to come up, it takes a long time to roll out during install.

Since it takes longer than 10 minutes, this triggers the new stalled-rollout heuristic, which causes us to go Degraded even though the network is not actually degraded. This is causing some confusion during bootstrap failures.

The fix is probably to ignore the multus-admission-controller.

Comment 1 Alexander Constantinescu 2020-01-27 16:24:09 UTC

Hi Weibin

I am moving this to MODIFIED. I think there was a screw-up with the naming of bugs on github which made this bug pass unnoticed. It's been fixed if you check the attached github link, so this should work.

/Alex

Comment 3 Weibin Liang 2020-01-27 18:52:03 UTC

Same PR is used in fixing https://bugzilla.redhat.com/show_bug.cgi?id=1779183 which was verified in 4.4.0-0.nightly-2020-01-06-072200

Comment 5 errata-xmlrpc 2020-05-04 11:16:20 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581