Bug 1762921 - fix multus-admission-controller definition to avoid spurious error messages
Summary: fix multus-admission-controller definition to avoid spurious error messages
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.2.z
Assignee: Douglas Smith
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On: 1764216
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-17 19:41 UTC by Dan Winship
Modified: 2019-10-30 04:45 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1764216 (view as bug list)
Environment:
Last Closed: 2019-10-30 04:45:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 343 0 None closed Bug 1762921: [4.2] The Multus admission controller should not have the not-ready toleration 2020-05-15 02:12:47 UTC
Red Hat Product Errata RHBA-2019:3151 0 None None None 2019-10-30 04:45:19 UTC

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
Note You need to log in before you can comment on or make changes to this bug.