Bug 1779183

Summary: Don't mark network operator un-Available or Degraded because of multus-admission-controller
Product: OpenShift Container Platform Reporter: Dan Winship <danw>
Component: NetworkingAssignee: Dan Winship <danw>
Networking sub component: openshift-sdn QA Contact: Weibin Liang <weliang>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified    
Version: 4.3.0   
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1779322 (view as bug list) Environment:
Last Closed: 2020-05-13 21:53:44 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:    
Bug Blocks: 1779322    

Description Dan Winship 2019-12-03 13:22:55 UTC 
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 3 Weibin Liang 2020-01-06 19:20:16 UTC 
Tested and verified on 4.4.0-0.nightly-2020-01-06-072200

CNO does not Degraded anymore just because multus-admission-controller is not available.
Comment 5 errata-xmlrpc 2020-05-13 21:53:44 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