Bug 1779322

Summary:	Don't mark network operator un-Available or Degraded because of multus-admission-controller
Product:	OpenShift Container Platform	Reporter:	Casey Callendrello <cdc>
Component:	Networking	Assignee:	Juan Luis de Sousa-Valadas <jdesousa>
Networking sub component:	openshift-sdn	QA Contact:	Weibin Liang <weliang>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	unspecified	CC:	danw, zzhao
Version:	4.3.0
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1779183	Environment:
Last Closed:	2020-01-23 11:17:46 UTC	Type:	---
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:	1779183
Bug Blocks:

Description Casey Callendrello 2019-12-03 18:40:28 UTC

+++ This bug was initially created as a clone of Bug #1779183 +++

CNO is responsible for deploying the multus-admission-controller, but unlike everything else it deploys, that is not necessary for "cluster networking" to be functional, and it can't start up until fairly late in the install. This means that if *anything* fails mid-install, the network operator will almost always be reporting not Available and (since https://github.com/openshift/cluster-network-operator/pull/358) eventually Degraded, causing people to mistakenly believe that the network was the cause of their install failure. We need to fix our status reporting to not imply that.

Comment 1 Casey Callendrello 2019-12-03 18:42:01 UTC

Juan, can you cherry-pick this to 4.3? Should be easy, just a few bot commands.

Comment 3 Weibin Liang 2019-12-05 19:09:36 UTC

Tested and verified on 4.3.0-0.nightly-2019-12-05-073829.

CNO will not Degraded anymore just because multus-admission-controller is not available.

Comment 5 errata-xmlrpc 2020-01-23 11:17:46 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:0062