Bug 2034908 - 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 8
Classification: Red Hat
Component: rhel-system-roles
Version: 8.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Zhiqian Guan
Mayur Patil
Whiteboard: role:network
Depends On:
Blocks: 2038956 2038957
TreeView+ depends on / blocked
Reported: 2021-12-22 13:19 UTC by Wen Liang
Modified: 2022-07-11 11:15 UTC (History)
10 users (show)

Fixed In Version: rhel-system-roles-1.13.0-1.el8
Doc Type: Bug Fix
Doc Text:
.The `nm` provider in the Networking System Role now correctly manages bridges Previously, if you used the `initscripts` provider, the Networking System Role created an `ifcfg` file which configured NetworkManager to mark bridge interfaces as unmanaged. Also, NetworkManager failed to detect followup `initscript` actions. For example, the `down` and `absent` actions of initscript provider will not change the NetworkManager's understanding on unmanaged state of this interface if not reloading the connection after the `down` and `absent` actions. With this fix, the Networking System Role uses the `NM.Client.reload_connections_async()` function to reload NetworkManager on managed hosts with NetworkManager 1.18. As a result, NetworkManager manages the bridge interface when switching the provider from `initscript` to `nm`.
Clone Of:
: 2038956 2038957 (view as bug list)
Last Closed: 2022-05-10 14:12:46 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github linux-system-roles network pull 446 0 None open Fix problem when switch provider from initscript to nm 2022-01-25 09:45:26 UTC
Red Hat Issue Tracker RHELPLAN-106409 0 None None None 2021-12-22 13:22:26 UTC
Red Hat Product Errata RHBA-2022:1896 0 None None None 2022-05-10 14:13:12 UTC

Description Wen Liang 2021-12-22 13:19:33 UTC
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 5 Zhiqian Guan 2022-02-10 07:44:26 UTC
:: [ 02:24:21 ] :: [   PASS   ] :: Test network/tests_ethernet_initscripts.yml (roles/rhel-system-roles.network/tests/tests_ethernet_initscripts.yml) with ANSIBLE-2.9 against RHEL_7_9_GA (Expected 0, got 0)
:: [ 02:25:38 ] :: [   PASS   ] :: Test network/tests_ethernet_nm.yml (roles/rhel-system-roles.network/tests/tests_ethernet_nm.yml) with ANSIBLE-2.9 against RHEL_7_9_GA (Expected 0, got 0)

[root@netqe18 Upstream-testsuite]# rpm -q rhel-system-roles
[root@netqe18 Upstream-testsuite]#

now the tests_ethernet_nm.yml playbook can pass after running tests_ethernet_initscripts.yml. Set this to verified

Comment 12 errata-xmlrpc 2022-05-10 14:12:46 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.


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