Bug 1762921

Summary: fix multus-admission-controller definition to avoid spurious error messages
Product: OpenShift Container Platform Reporter: Dan Winship <danw>
Component: NetworkingAssignee: Douglas Smith <dosmith>
Networking sub component: openshift-sdn QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified    
Version: 4.3.0   
Target Milestone: ---   
Target Release: 4.2.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1764216 (view as bug list) Environment:
Last Closed: 2019-10-30 04:45:14 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: 1764216    
Bug Blocks:    

Description Dan Winship 2019-10-17 19:41:49 UTC 
The multus-admission-controller pod currently tolerates "not-ready", which means it can be scheduled to a node before networking is up, but then it repeatedly fails to start with "blah blah no CNI plugin blah blah" errors. This got fixed in 4.3 but missed the 4.2 freeze.
Comment 3 zhaozhanqi 2019-10-23 06:38:29 UTC 
Verified this bug on 4.2.0-0.nightly-2019-10-23-011659

# oc get ds -n openshift-multus multus-admission-controller -o yaml | grep tolerations -A 4
      tolerations:
      - effect: NoSchedule
        key: node-role.kubernetes.io/master
        operator: Exists
      volumes:
Comment 5 errata-xmlrpc 2019-10-30 04:45:14 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-2019:3151