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.
Bug 1540218 - ovs ports are still visible when ovs master bridge is removed
Summary: ovs ports are still visible when ovs master bridge is removed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Lubomir Rintel
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1654714
TreeView+ depends on / blocked
 
Reported: 2018-01-30 13:42 UTC by Vladimir Benes
Modified: 2019-08-06 13:16 UTC (History)
10 users (show)

Fixed In Version: NetworkManager-1.16.2-0.1.20190328git8ec0954570.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-06 13:16:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2302 0 None None None 2019-08-06 13:16:36 UTC

Description Vladimir Benes 2018-01-30 13:42:25 UTC 
Description of problem:
This works well:
nmcli conn add conn.type ovs-bridge conn.interface bridge0
nmcli conn add conn.type ovs-port conn.interface port0 conn.master bridge0
nmcli conn add conn.type ovs-port conn.interface port1 conn.master bridge0
nmcli conn add type ethernet conn.interface eth2 conn.master port1 slave-type ovs-port
nmcli conn add type ethernet conn.interface eth3 conn.master bond0 slave-type ovs-port
nmcli conn add conn.type ovs-interface conn.interface iface0 conn.master port0 


But after calling:
nmcli connection delete id ovs-bridge-bridge0
I see:
DEVICE  TYPE      STATE         CONNECTION 
eth0    ethernet  connected     testeth0   
eth1    ethernet  disconnected  --         
eth10   ethernet  disconnected  --         
eth2    ethernet  disconnected  --         
eth3    ethernet  disconnected  --         
eth4    ethernet  disconnected  --         
eth5    ethernet  disconnected  --         
eth6    ethernet  disconnected  --         
eth7    ethernet  disconnected  --         
eth8    ethernet  disconnected  --         
eth9    ethernet  disconnected  --         
port0   ovs-port  disconnected  --         
port1   ovs-port  disconnected  --         
lo      loopback  unmanaged     --         
9a5deece-708c-443f-8aea-0053d6e3b0ca
    ovs_version: "2.8.0"


These ovs-ports devices should be gone too.


Version-Release number of selected component (if applicable):
openvswitch-2.8.0-3.el7fdb.x86_64
NetworkManager-1.10.2-9.el7.x86_64
Comment 4 Vladimir Benes 2019-03-07 14:45:42 UTC 
I can see ovs-interface too:
iface0   ovs-interface  disconnected  --         

this si reproducible by running ove_openvswitch_ports_and_master_bridge_configuration in a while cycle until it fails (~10 cycles)

I am running it with openvswitch-2.9.0-92.el7fdn.x86_64
Comment 5 Lubomir Rintel 2019-03-26 14:38:42 UTC 
Fixed by:

https://github.com/NetworkManager/NetworkManager/pull/315
https://github.com/NetworkManager/NetworkManager/pull/320
Comment 7 Vladimir Benes 2019-04-01 08:21:23 UTC 
setting things up:
nmcli conn add conn.type ovs-bridge conn.interface bridge0
nmcli conn add conn.type ovs-port conn.interface port0 conn.master bridge0
nmcli conn add conn.type ovs-port conn.interface port1 conn.master bridge0
nmcli conn add type ethernet conn.interface eth2 conn.master port1 slave-type ovs-port
nmcli conn add type ethernet conn.interface eth3 conn.master bond0 slave-type ovs-port
nmcli conn add conn.type ovs-interface conn.interface iface0 conn.master port0 

running this after everything is up:
nmcli connection delete id ovs-bridge-bridge0

leads to:
[root@gsm-r5s10-01 NetworkManager-ci]# nmcli connection 
NAME                  UUID                                  TYPE           DEVICE 
testeth0              be8be67e-90ec-4a45-8049-58ad26ed0032  ethernet       eth0   
ovs-interface-iface0  62703849-3068-4a1f-8eb4-20d4f4ec50f9  ovs-interface  --     
ovs-port-port0        dd9b4557-f2cf-4cd0-9480-4db44634c961  ovs-port       --     
ovs-port-port1        b41892b1-a5b0-48ae-bec6-0bed6f6d03db  ovs-port       --     
ovs-slave-eth2        efac7af0-3e64-424a-8ab0-4489569cfa1a  ethernet       --     
ovs-slave-eth3        7de0143e-c0c0-43c1-89dd-a618b3e6341b  ethernet       --     
testeth1              ba3e775d-7170-41b9-821a-fcf9711611ac  ethernet       --     
testeth10             72fd6fb1-6fc8-44dd-b871-9ade1bfb40ec  ethernet       --     
testeth2              14a15a94-c971-475c-a4ef-53cd87769ef9  ethernet       --     
testeth3              82ea5ace-fc25-4ea1-9e40-e5f534a1f11a  ethernet       --     
testeth4              631f3356-41fe-4007-9714-08a9fe85b472  ethernet       --     
testeth5              3d10ac18-8070-43e1-af34-0d1389a1fe1c  ethernet       --     
testeth6              73b2ae76-3d3f-43ea-afe0-4c5ceed62dff  ethernet       --     
testeth7              8028299f-a502-4a9f-a9fd-fd3479715a5a  ethernet       --     
testeth8              3310bf01-027b-4042-b836-0ab27a37b5c4  ethernet       --     
testeth9              c71cd27b-e43c-4253-ad5c-ac57154e14d3  ethernet       --     
[root@gsm-r5s10-01 NetworkManager-ci]# nmcli device 
DEVICE  TYPE      STATE         CONNECTION 
eth0    ethernet  connected     testeth0   
eth1    ethernet  disconnected  --         
eth10   ethernet  disconnected  --         
eth2    ethernet  disconnected  --         
eth3    ethernet  disconnected  --         
eth4    ethernet  disconnected  --         
eth5    ethernet  disconnected  --         
eth6    ethernet  disconnected  --         
eth7    ethernet  disconnected  --         
eth8    ethernet  disconnected  --         
eth9    ethernet  disconnected  --         
port1   ovs-port  disconnected  --         
lo      loopback  unmanaged     --         
[root@gsm-r5s10-01 NetworkManager-ci]# ovs-vsctl show
c7281048-33d2-4a37-be72-d726040e547c
    ovs_version: "2.9.0"

so there is still stalled port1 left behind.
Comment 8 Lubomir Rintel 2019-04-09 06:27:01 UTC 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/0b51fd6447
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/fc5003f750
Comment 9 Vladimir Benes 2019-04-09 13:59:05 UTC 
working well now
Comment 11 errata-xmlrpc 2019-08-06 13:16:20 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-2019:2302
Note You need to log in before you can comment on or make changes to this bug.