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.
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.
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?
(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.
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
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.