Description of problem: See https://bugzilla.redhat.com/show_bug.cgi?id=1885517 for full description. tl;dr from old local gateway mode in 4.5 -> 4.6 upgrade we are not cleaning up an old port from the previous gateway mode (br-local_<node name>). This is not applicable to 4.7, because this port will never exist in 4.6->4.7 upgrade on the external switch. Way to verify on a new 4.6 setup, look at ovn-nbctl external switch (ext_<node name>): switch 89dea851-8220-4ae2-9881-704c79e61dae (ext_worker-0-0) port etor-GR_worker-0-0 type: router addresses: ["52:54:00:94:dc:86"] router-port: rtoe-GR_worker-0-0 port br-ex_worker-0-0 type: localnet addresses: ["unknown"] It should only have br-ex_<node name> as a localnet type port. In 4.5->4.6 upgrade with current bug, the following port is leftover: switch 89dea851-8220-4ae2-9881-704c79e61dae (ext_worker-0-0) port etor-GR_worker-0-0 type: router addresses: ["52:54:00:94:dc:86"] router-port: rtoe-GR_worker-0-0 port br-ex_worker-0-0 type: localnet addresses: ["unknown"] port br-local_worker-0-0 <------leftover from 4.5 type: localnet addresses: ["unknown"]
QE please confirm we can skip fixing this for 4.7 since it is only applicable to 4.5->4.6 upgrade.
Only needed for 4.6
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633