-
Bug
-
Resolution: Done
-
Undefined
-
4.16.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
Done
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-59929. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-59928. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-57484. The following is the description of the original issue:
—
Description of problem:
After OpenShiftSDN to OVN-K live migration with custom NMstate, br0 is left on the system.
- name: br0
type: ovs-interface
state: ignore
mtu: 1450
ipv4:
enabled: false
ipv6:
enabled: false
controller: br0
accept-all-mac-addresses: false
Version-Release number of selected component (if applicable):
4.16.38
How reproducible:
Once
Steps to Reproduce:
1. install OpenShift SDN 4.14.50 and configure balance-slb OVS bonds using nmstate https://github.com/RHsyseng/rhcos-slb/blob/simplify-networking/README.md 2. upgrade to 4.15 3. upgrade to 4.16.38 4. apply OVN-K live migration workarounds https://github.com/rbbratta/rhcos-slb/blob/sdn-to-ovn-migration/sdn-to-ovn/README.md 5. live migrate to OVN-K 6. wait
Actual results:
br0 present
Expected results:
br0 not present
Additional info:
Custom NMstate was used to remove extra brcnv, this occurs after the first reboot?
- name: brcnv
type: ovs-interface
state: absent
At what point in the live-migration can we remove br0?
- blocks
-
-
- Closed
-
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to
