Bug 1809289

Summary: [4.5] Multus should not cause machine to go not ready when Multus is updated
Product: OpenShift Container Platform Reporter: Douglas Smith <dosmith>
Component: NetworkingAssignee: Douglas Smith <dosmith>
Networking sub component: multus QA Contact: Weibin Liang <weliang>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: jeder, weliang, zzhao
Version: unspecified   
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1809285 Environment:
Last Closed: 2020-07-13 17:17:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1809285    

Description Douglas Smith 2020-03-02 19:11:28 UTC
+++ This bug was initially created as a clone of Bug #1809285 +++

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

Description of problem: When Multus is upgraded it invalidates the primary CNI configuration on each node as it is upgraded. This causes unnecessary delays, and can result

How reproducible: During upgrades.

Additional info: One of the fixes for https://bugzilla.redhat.com/show_bug.cgi?id=1793635

--- Additional comment from Douglas Smith on 2020-03-02 19:09:00 UTC ---

PR @ https://github.com/openshift/multus-cni/pull/52

Comment 1 Douglas Smith 2020-03-02 19:13:22 UTC
PR has landed @ https://github.com/openshift/multus-cni/pull/50

@Weibin -- to validate, make sure that the /entrypoint.sh does not contain the string "invalid"

cat /entrypoint.sh | grep -i invalid

Comment 5 errata-xmlrpc 2020-07-13 17:17:29 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.