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
PR @ https://github.com/openshift/multus-cni/pull/52
Tested and verified in 4.3.0-0.nightly-2020-03-12-085147 [root@dhcp-41-193 FILE]# oc get clusterversions NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.3.0-0.nightly-2020-03-12-085147 True False 128m Cluster version is 4.3.0-0.nightly-2020-03-12-085147 [root@dhcp-41-193 FILE]# oc rsh multus-bg99w sh-4.2# cat /entrypoint.sh | grep -i invalid sh-4.2# exit
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:0858