Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1823493

Summary: [4.5] Multus CNI should perform readiness check on CNI DEL
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: weliang
Version: 4.5   
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1823490 Environment:
Last Closed: 2020-07-13 17:27:23 UTC Type: ---
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:    
Bug Blocks: 1823490    

Description Douglas Smith 2020-04-13 20:05:34 UTC
+++ This bug was initially created as a clone of Bug #1823490 +++

Reported by Clayton Coleman while improving upgrades, this is for correctness during CNI DEL.

PR exists for 4.4 exists @ https://github.com/openshift/multus-cni/pull/56

Comment 1 Douglas Smith 2020-04-13 20:06:00 UTC
PR merged @ https://github.com/openshift/multus-cni/pull/54

Comment 2 Douglas Smith 2020-04-13 20:08:53 UTC
This is merged and will be required to be verified, however, testing this functionality is... Not straightforward. I'll need to think about how this can be done.

Comment 3 Weibin Liang 2020-04-15 19:32:59 UTC
Tested and verified in 4.4.0-0.nightly-2020-04-15-152338

During an upgrade from v4.4 to v4.5, when the machine is rebooted I don't see anything in node journal logs around "no default network" after reboot

Comment 5 errata-xmlrpc 2020-07-13 17:27:23 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-2020:2409