Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionBeniamino Galvani
2022-11-28 14:47:06 UTC
When a virtual interface is created outside of NetworkManager and attached to an ovs bridge, after disabling and re-enabling networking multiple times via "nmcli networking off; nmcli networking on", NetworkManager brings the interface down. This can be reproduced with the following commands:
ip link add vxlan1 type vxlan remote 172.25.12.1 id 120 dstport 0
ip link set vxlan1 up
ovs-vsctl add-br br1
ovs-vsctl add-port br1 vxlan1
ovs-vsctl show
ip link show vxlan1
nmcli networking off
nmcli networking on
sleep 1
nmcli networking off
nmcli networking on
ovs-vsctl show
ip link show vxlan1
At the end, vxlan1 is down:
272: vxlan1: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue master ovs-system state DOWN mode DEFAULT group default qlen 1000
The expected result is that the interface is not touched by NM since it was created externally.
Affected versions:
NetworkManager 1.30, NetworkManager 1.40, current git main
Comment 1Beniamino Galvani
2022-11-28 14:55:29 UTC
Initially, the vxlan is in disconnected state and is considered 'external'.
[1669644967.4654] device (vxlan1): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external')
The problem is that after toggling networking, the 'external' state is lost and the device becomes fully managed.
[1669644995.0894] device (vxlan1): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'external')
[1669645001.8996] device (vxlan1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
[1669645001.9245] device (vxlan1): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
At this point a "networking off" will bring the interface down.
after a certain amount of repetitions, I still see missing LOWER_UP
see attachment
Comment 20Beniamino Galvani
2023-05-29 08:37:44 UTC
> adding may_fail tag to the ovs_vxlan_networking_off_on test
I couldn't reproduce the new failure with the NMCI test, but according to logs it seems caused by a race condition in NM that makes the external device fully managed by NM
By stopping and resuming NM at the right time the issue is 100% reproducible:
# Temporarily stop NetworkManager to trigger the race condition, which
# happens when NM detects the interface already attached to the OVS
# bridge and already announced by udev.
killall -STOP NetworkManager
ip link add vxlan1 type vxlan remote 172.25.12.1 id 120 dstport 0
ip link set vxlan1 up
ovs-vsctl add-br br1
ovs-vsctl add-port br1 vxlan1
sleep .4
killall -CONT NetworkManager
ovs-vsctl show
ip link show vxlan1
nmcli networking off
nmcli networking on
sleep 1
nmcli networking off
nmcli networking on
ovs-vsctl show
ip link show vxlan1
# vxlan1 is DOWN now
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 (NetworkManager 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/RHBA-2023:6585