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 1935026 - cannot delete ovs bridge
Summary: cannot delete ovs bridge
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2022-03-14
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.3
Hardware: Unspecified
OS: Unspecified
urgent
unspecified
Target Milestone: rc
: ---
Assignee: Fernando F. Mancera
QA Contact: Vladimir Benes
URL:
Whiteboard:
Depends On:
Blocks: 2061709 2062606
TreeView+ depends on / blocked
 
Reported: 2021-03-04 09:34 UTC by Vladimir Benes
Modified: 2022-05-10 15:30 UTC (History)
12 users (show)

Fixed In Version: NetworkManager-1.36.0-3.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2061709 2062606 (view as bug list)
Environment:
Last Closed: 2022-05-10 14:54:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
reproducer (3.07 KB, text/plain)
2021-03-04 09:36 UTC, Vladimir Benes 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 1084 0 None closed ovs-port: always remove the OVSDB entry on slave release 2022-02-09 13:22:56 UTC
freedesktop.org Gitlab NetworkManager NetworkManager merge_requests 1119 0 None closed ovs-port: fix removal of ovsdb entry if the interface goes away 2022-03-09 09:57:07 UTC

Description Vladimir Benes 2021-03-04 09:34:40 UTC 
Description of problem:
I have a script for ovs-nmstate test, at the end I delete all profiles but the bridge is not correctly deleted

nmcli connection delete id bond_test bond_test.3 br_test ovs-br0 ovs-port-ovs1 ovs-port-veth0c ovs-port-veth0r ovs-port-veth1c ovs1 veth0c veth0c_p veth0r  veth1c veth1c_p veth1r || true

->

[root@beaker-networkmanager-gitlab-trigger-test-upstream-1375 NetworkManager-ci]# ovs-vsctl show
fc901299-8d22-4cac-91a8-46eb82891a8c
    Bridge ovs-br0
        Port ovs-port-veth0r
            Interface veth0r
                type: system
                error: "could not open network device veth0r (No such device)"
        Port ovs-port-veth0c
            Interface veth0c
                type: system
                error: "could not open network device veth0c (No such device)"
        Port ovs-port-veth1c
            Interface veth1c
                type: system
                error: "could not open network device veth1c (No such device)"
    ovs_version: "2.13.2"



Version-Release number of selected component (if applicable):
NetworkManager-1.30.0-1.el8.x86_64
nmstate-1.0.2-1.el8.noarch
openvswitch2.13-2.13.0-79.5.el8fdp.x86_64


How reproducible:
always

Steps to Reproduce:
1. run two times script attached

Actual results:
the second run fails
Comment 1 Vladimir Benes 2021-03-04 09:36:07 UTC 
Created attachment 1760638 [details]
reproducer
Comment 5 Lubomir Rintel 2022-02-03 10:34:40 UTC 
In review: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1084
Comment 6 Lubomir Rintel 2022-02-03 12:42:50 UTC 
Merged
Comment 7 Beniamino Galvani 2022-02-10 15:55:33 UTC 
Problem reproduced with NM 405afad0a621ed4411a0297e546c2787103886d1
(before the fix):

# ./repro_1923248.sh
[...]
# ovs-vsctl show
c83120f0-5a0e-439b-9b74-7d6ea6fa7f1c
    Bridge ovs-br0
	Port ovs-port-veth0r
            Interface veth0r
		type: system
		error: "could not open network device veth0r (No such device)"
	Port ovs-port-veth0c
            Interface veth0c
		type: system
		error: "could not open network device veth0c (No such device)"
	Port ovs-port-veth1c
            Interface veth1c
		type: system
		error: "could not open network device veth1c (No such device)"
    ovs_version: "2.15.0"

The problem doesn't happen after the fix.
Comment 10 Vladimir Benes 2022-02-21 12:37:55 UTC 
covered in https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/964
regression found:
https://bugzilla.redhat.com/show_bug.cgi?id=2055665
Comment 12 Vladimir Benes 2022-02-28 16:46:30 UTC 
This is unfixed as fixes for #2047302 or #2029937 or 2022275 broke it again.
Comment 23 Gris Ge 2022-03-08 14:56:45 UTC 
Exception request notes:


======= Impact Statement ======= 

What is the benefit of making this change after the deadline? What is the impact on customer satisfaction, and on the business?

The OpenvSwitch plugin of NetworkManager is widely used in RHV and CNV team. Deleting an OpenvSwtich bridge is considered as key function.
The problem was fixed by early rpm build of 8.6, but then been reintroduced by late patches.

What is the risk to the release schedule, quality, and the impact of diverting resources from other efforts? Will there be enough time to do the necessary large-scale, cross-function, regression, stress, or fault-insertion testing that may be required to verify this change? 

Upstream has merged the patch.
Scratch build been tested at comment #17
CI has confirmed no regression been introduced for know use cases.
NetworkManager QE(Vladimír Beneš <vbenes>) confirmed there is enough resources for testing new rpm build
as the CI results only require up to 2 days for log vetting.
Comment 25 Vladimir Benes 2022-03-18 10:27:05 UTC 
failing with RHEL-8.6.0-20220308.2  and not failing with RHEL-8.6.0-20220318.d.0
Comment 27 errata-xmlrpc 2022-05-10 14:54:08 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 (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/RHEA-2022:1985
Note You need to log in before you can comment on or make changes to this bug.