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 2038956 - Failure to activate connection: nm-manager-error-quark: No suitable device found for this connection
Summary: Failure to activate connection: nm-manager-error-quark: No suitable device fo...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rhel-system-roles
Version: 7.9
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Jakub Haruda
Whiteboard: role:network
Depends On: 2034908 2038957
TreeView+ depends on / blocked
Reported: 2022-01-10 16:05 UTC by Noriko Hosoi
Modified: 2022-03-30 13:54 UTC (History)
9 users (show)

Fixed In Version: rhel-system-roles-1.7.3-3.el7_9
Doc Type: Bug Fix
Doc Text:
Cause: In initscript mode, network role will create ifcfg file with `NM_CONTROLLED=no` instructing NetworkManager to mark the bridge as unmanaged. The follow up `down` and `absent` action of initscript provider will not change the NetworkManager's understanding on unmanaged state of this interface if the version of NetworkManager is 1.18. Fixes: Use `NM.Client.reload_connections_async()` to reload the configuration for nm provider on NetworkManager 1.18. Result: With the fixes, when switching the provider from the initscripts to the nm, the system will manage the bridge device.
Clone Of: 2034908
Last Closed: 2022-02-22 18:56:17 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github linux-system-roles network pull 446 0 None Merged Fix problem when switch provider from initscript to nm 2022-01-28 18:21:35 UTC
Red Hat Issue Tracker RHELPLAN-107307 0 None None None 2022-01-10 16:17:11 UTC
Red Hat Product Errata RHBA-2022:0644 0 None None None 2022-02-22 18:56:27 UTC

Description Noriko Hosoi 2022-01-10 16:05:40 UTC
+++ This bug was initially created as a clone of Bug #2034908 +++

Description of problem:

The system role build `rhel-system-roles-1.7.3-2.el7_9` CI gating failed on
`tests_ethernet_nm.yml` (https://dashboard.osci.redhat.com/#/artifact/brew-build/aid/41866280?focus=id:7faf82018486-1)
and the failures indicated that the the created veth device is strictly unmanaged even if we explicitly set it to managed.

nmcli d set lsr27 managed yes

Dec 20 19:39:10 ibm-p8-kvm-03-guest-02.virt.pnr.lab.eng.rdu2.redhat.com NetworkManager[738]: <info>  [1640047150.4781] audit: op="device-managed" arg="managed" pid=19292 uid=0 result="success" (Journal)

(nmcli d)
eth0       ethernet  connected     System eth0
peerlsr27  ethernet  disconnected  --          
lsr27      ethernet  unmanaged     --          

The situation arised only when the last test playbook is  `tests_ethernet_initscripts.yml`, when initscripts provider ran, the connection profile (/etc/sysconfig/network-scripts/ifcfg-lsr27) contained `NM_CONTROLLED=no`, which indicated that the device lsr27 is not managed by NM and at the end we cleaned the device and profile then when NM provider ran, we have to reload the connection because the connection profile was deleted (changed) previously. The test palybooks `tests_auto_gateway_nm.yml`, `tests_ipv6_nm.yml`, `tests_vlan _mtu_nm.yml` ran into the same issue. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Download rhel-guest-image-7.9-30.x86_64.qcow2 from http://download.hosts.prod.upshift.rdu2.redhat.com/released/rhel-6-7-8/rhel-7/RHEL-7/7.9/Server/x86_64/images/rhel-guest-image-7.9-30.x86_64.qcow2

2. `sudo TEST_DEBUG=1 TEST_SUBJECTS=rhel-guest-image-7.9-30.x86_64.qcow2 ansible-playbook -v -i /usr/share/ansible/inventory/standard-inventory-qcow2  ./tests/tests_ethernet_initscripts.yml ./tests/tests_ethernet_nm.yml`

Actual results:
Errors: "state:up persistent_state:present, 'lsr27': up connection failed: failure to activate connection: nm-manager-error-quark: No suitable device found for this connection"

Expected results:
No errors 

Additional info:

Comment 12 Wen Liang 2022-02-01 17:01:23 UTC

Comment 18 errata-xmlrpc 2022-02-22 18:56:17 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 (rhel-system-roles 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.


Comment 19 Wen Liang 2022-03-30 13:54:54 UTC
clear needinfo

Note You need to log in before you can comment on or make changes to this bug.