-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-9.4.z
-
NetworkManager-1.51.2-1.el9
-
No
-
Moderate
-
ZStream
-
rhel-sst-network-management
-
ssg_networking
-
9
-
5
-
False
-
-
None
-
None
-
Approved Blocker
-
-
Pass
-
None
-
None
What were you trying to do that didn't work?
After nmstate invoked `connection-delete`, we noticed the NM connection is deleted as expected but OVS interface still exists both in kernel and OVS database.
Please provide the package NVR for which bug is seen:
NetworkManager-1.49.3-33394.copr.a367f8770b.el9.x86_64
How reproducible:
10%
Steps to reproduce
wget https://people.redhat.com/fge/ovs_leftover/https://people.redhat.com/fge/ovs_leftover/ovs_leftover.py dnf install -y https://people.redhat.com/fge/ovs_leftover/nmstate.ovsleftover.el9.x86_64.rpm sudo python3 ./ovs_leftover.py
Expected results
No error
Actual results
libnmstate.error.NmstateVerificationError: Absent/Down interface br0/ovs-bridge still found
Notes
- The nmstate used for reproducing is from https://github.com/nmstate/nmstate/pull/2739 which just set OVS-port connection.autoconnect-ports to true.
- The output indicate after NM connection been deleted, the OVS database still has full OVS bridge.
- blocks
-
RHEL-56095 Change the OVN localnet to absent causes leftover OVS bridge
- Closed
- links to
-
RHBA-2024:138504 NetworkManager bug fix and enhancement update