Bug 1935026

Summary: cannot delete ovs bridge
Product: Red Hat Enterprise Linux 8 Reporter: Vladimir Benes <vbenes>
Component: NetworkManagerAssignee: Fernando F. Mancera <ferferna>
Status: CLOSED ERRATA QA Contact: Vladimir Benes <vbenes>
Severity: unspecified Docs Contact:
Priority: urgent    
Version: 8.3CC: acardace, bgalvani, ferferna, fge, fpokryvk, jwboyer, lmiksik, lrintel, rkhan, sukulkar, thaller, till
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.36.0-3.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2061709 2062606 (view as bug list) Environment:
Last Closed: 2022-05-10 14:54:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2061709, 2062606    
Deadline: 2022-03-14   
Attachments:
Description Flags
reproducer none

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 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 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