Bug 1700528

Summary: NetworkManager fails to activate profile on newer CentOS 7 docker image
Product: Red Hat Enterprise Linux 8 Reporter: Till Maas <till>
Component: NetworkManagerAssignee: NetworkManager Development Team <nm-team>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.3CC: atragler, bgalvani, fgiudici, jkucera, lrintel, pasik, pcahyna, rkhan, sukulkar, thaller, vcrhonek
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-18 15:21:30 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:
Attachments:
Description Flags
NetworkManager trace log for tests_ethernet_other_provider.yml
none
NM trace for tests_bridge_other_provider none

Description Till Maas 2019-04-16 19:56:06 UTC 
Created attachment 1555647 [details]
NetworkManager trace log for tests_ethernet_other_provider.yml

Description of problem:
Running a test from the network rhel system role fails:


TEST_DEBUG=1 TEST_DOCKER_EXTRA_ARGS="-it --privileged -v /sys/fs/cgroup:/sys/fs/cgroup:ro" TEST_SUBJECTS=docker:vcrhonek/centos7-systemd  ansible-playbook -i $HOME/standard-test-roles/inventory/standard-inventory-docker  tests/helpers/nm-trace-logging.yml 
tests/tests_ethernet_other_provider.yml

TASK [linux-system-roles.network : Configure networking connection profiles] ********************************************************************************
 [WARNING]: [003] <info>  #0, state:up persistent_state:present, 'lsr27': add connection lsr27, 3e16a8fc-ce03-4516-9ac5-9edc055db42f

 [WARNING]: [004] <info>  #0, state:up persistent_state:present, 'lsr27': up connection lsr27, 3e16a8fc-ce03-4516-9ac5-9edc055db42f (not-active)

 [WARNING]: [005] <error> #0, state:up persistent_state:present, 'lsr27': up connection failed: failure to activate connection: nm-manager-error-quark: No
suitable device found for this connection. (3)

fatal: [924faf51e3e54e52d7de64fe0ac25a1ff76fc2cedeb01a2a7bae0a6f40e96224]: FAILED! => {"changed": true, "msg": "error: up connection failed: failure to activate connection: nm-manager-error-quark: No suitable device found for this connection. (3)"}
	to retry, use: --limit @/home/vagrant/network-lsr/tests/tests_ethernet_other_provider.retry


It works with this (older) docker image:
docker.io/milcom/centos7-systemd     latest              97819b9ad572        12 months ago       202 MB


How reproducible:
always



Additional info:
This was run with https://pagure.io/standard-test-roles/pull-request/332 applied

Trace logging playbook:

cat > 'tests/helpers/nm-trace-logging.yml' <<EOF
# SPDX-License-Identifier: BSD-3-Clause
---
- hosts: all
  tasks:
    - file:
        dest: /etc/NetworkManager/conf.d/
        state: directory
    - copy:
        dest: /etc/NetworkManager/conf.d/trace-logging.conf
        content: |
          [logging]
          level=TRACE
          domains=ALL
    - service:
        name: NetworkManager
        state: restarted
      ignore_errors: true
EOF

Test playbook: https://github.com/linux-system-roles/network/blob/master/tests/tests_ethernet_other_provider.yml
Comment 2 Till Maas 2019-04-16 20:08:48 UTC 
Created attachment 1555660 [details]
NM trace for tests_bridge_other_provider

There is a similar error for the tests_bridge_other_provider.yml playbook


TASK [linux-system-roles.network : Configure networking connection profiles] *****************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
 [WARNING]: [003] <info>  #0, state:up persistent_state:present, 'LSR-TST-br31': add connection LSR-TST-br31, f86efeb5-4275-446d-b713-7873114c8dc1

 [WARNING]: [004] <info>  #0, state:up persistent_state:present, 'LSR-TST-br31': up connection LSR-TST-br31, f86efeb5-4275-446d-b713-7873114c8dc1 (not-active)

 [WARNING]: [005] <error> #0, state:up persistent_state:present, 'LSR-TST-br31': up connection failed: failure to activate connection: nm-manager-error-quark: Connection 'LSR-TST-br31' is not available on the device LSR-TST-br31 at this time. (2)

fatal: [0ff2de9b584e0a41bda8f268961723574db41d1a4bcc2c6492908ad2aacd3856]: FAILED! => {"changed": true, "msg": "error: up connection failed: failure to activate connection: nm-manager-error-quark: Connection 'LSR-TST-br31' is not available on the device LSR-TST-br31 at this time. (2)"}
Comment 3 Beniamino Galvani 2019-04-17 07:05:35 UTC 
This looks similar to bug 1667874.
Comment 4 Pavel Cahyna 2019-04-17 09:31:42 UTC 
jkucera, vcrhonek: haven't you seen something similar as well? IIRC for bond or team devices? https://github.com/linux-system-roles/network/issues/102 looks a bit similar as well.
Comment 6 Beniamino Galvani 2020-03-30 09:53:36 UTC 
Hi Till,

this bz could be the same issue as bug 1667874, which is already solved.

Can you confirm whether the problem happens in RHEL 8.2?
Comment 10 Thomas Haller 2021-01-18 15:21:30 UTC 
(In reply to Beniamino Galvani from comment #6)
> Hi Till,
> 
> this bz could be the same issue as bug 1667874, which is already solved.
> 
> Can you confirm whether the problem happens in RHEL 8.2?

This is probably fixed. Please reopen if not. Thank you!