Bug 2052441

Summary: Activation on OVS system interface should fail when OVS daemon not started
Product: Red Hat Enterprise Linux 8 Reporter: Gris Ge <fge>
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: CLOSED ERRATA QA Contact: Vladimir Benes <vbenes>
Severity: low Docs Contact:
Priority: low    
Version: 8.6CC: bgalvani, ferferna, lrintel, rkhan, sfaye, sukulkar, till, vbenes
Target Milestone: rcKeywords: Reopened, Triaged
Target Release: 8.7   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: NetworkManager-1.39.3-1.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2089860 (view as bug list) Environment:
Last Closed: 2022-11-08 10:07:32 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: 2089860    
Attachments:
Description Flags
bug.sh none

Description Gris Ge 2022-02-09 09:51:21 UTC
Created attachment 1860020 [details]
bug.sh

Description of problem:

In NM 1.30, `nmcli c up eth1` will fail when eth1 is OVS system interface and OVS daemon not started.

In NM 1.36, `nmcli c up eth1` passes.


Version-Release number of selected component (if applicable):
NetworkManager-1.36.0-0.7.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. sudo ./bug.sh
2.
3.

Actual results:

No failure.

Expected results:

Error: Connection activation failed: Open vSwitch database connection failed

Additional info:

NetworkManager-1.30.0-13.el8_4 will fail the activation as expected.

For OVS internal interface, activation fail as expected in NM 1.36.

Comment 1 Gris Ge 2022-02-09 09:52:41 UTC
Created attachment 1860021 [details]
System logs with NM trace enabled

Comment 2 Gris Ge 2022-02-09 09:53:08 UTC
This is low priority.

Comment 4 Gris Ge 2022-03-05 10:59:45 UTC
This has been fixed by NetworkManager-1.36.0-2.el8.x86_64

Comment 5 Gris Ge 2022-03-05 11:20:23 UTC
Hi Beniamino,

This problem is fixed in NetworkManager-1.36.0-2.el8.x86_64, but reproduceable in NetworkManager-1:1.37.1-29888.copr.f1b3dd4eb5.el8.

Could you check whether main branch missing any patches?

Comment 6 Gris Ge 2022-03-07 12:41:31 UTC
Let's reopen this bug. Even RHEL 8.6 fixed this problem, RHEL 8.7 will has.

Comment 8 Thomas Haller 2022-03-07 12:55:33 UTC
(In reply to Gris Ge from comment #5)
> Hi Beniamino,
> 
> This problem is fixed in NetworkManager-1.36.0-2.el8.x86_64, but
> reproduceable in NetworkManager-1:1.37.1-29888.copr.f1b3dd4eb5.el8.
> 
> Could you check whether main branch missing any patches?

That would be surprising.

Patches always go "main" -> "nm-1-36" -> "rhel-8.6.0", never(*) any other way.
In particular not "main" -> "rhel-8.6.0" or "nm-1-36" -> "main".

If you do `gitk origin/nm-1-36 origin/main` you see that the "cherry picked from" comments on `nm-1-36` refer to commits from `main`.


(*) sometimes there might be exceptions, if the patch only makes sense for the older branch. Then we would also do "original work" on the old branch, instead of just backporting. That happens only seldom.

Comment 9 Gris Ge 2022-03-31 01:59:06 UTC
NetworkManager-1.37.2-1.el8.x86_64 works well now. Closing.

Comment 10 Gris Ge 2022-04-01 13:54:50 UTC
Problem happen again on NetworkManager-1.37.3-30055.copr.586afdfc52.el8.x86_64:


https://github.com/nmstate/nmstate/runs/5785031223?check_suite_focus=true


The same test passes on NetworkManager-1.37.2-1.el9.x86_64

Comment 17 errata-xmlrpc 2022-11-08 10:07:32 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/RHBA-2022:7680