+++ 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
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 ```
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:2409