Bug 2062494

Summary: pytest failed when running with nm providers in the rhel-8.5 beaker machine
Product: Red Hat Enterprise Linux 8 Reporter: Wen Liang <wenliang>
Component: rhel-system-rolesAssignee: Rich Megginson <rmeggins>
Status: CLOSED DUPLICATE QA Contact: David Jež <djez>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.5CC: djez, nhosoi, spetrosi
Target Milestone: rcKeywords: Bugfix, Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: role:network
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2064396 (view as bug list) Environment:
Last Closed: 2022-04-27 22:49:01 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: 2064396, 2064401    

Description Wen Liang 2022-03-09 22:40:47 UTC 
Description of problem:

```error
ansible_collections.redhat.rhel_system_roles.plugins.module_utils.network_lsr.myerror.MyError: failure to activate connection: nm-manager-error-quark: No suitable device found for this connection (device enp0s1 not available because profile is not compatible with device (mismatching interface name)). 
```

https://beaker-archive.host.prod.eng.bos.redhat.com/beaker-logs/2022/02/63394/6339461/11521985/140366957/SYSTEM-ROLE-network_tests_integration_pytest.yml-collections-ANSIBLE-2.log


Running the pytest with nm provider failed in the downstream testing
because the "NM_CONTROLLED=no" appeared in
/etc/sysconfig/network-scripts/ifcfg-testeth which caused the veth
testeth strictly unmanaged by NetworkManager. 



Steps to Reproduce:
1. Running the integration test `./tests/tests_integration_pytest.yml` against a rhel-8.5 beaker machine 
`TEST_DEBUG=1  ansible-playbook -v -i inventory.ini  ./tests/tests_integration_pytest.yml`


Actual results:
Running the pytest with nm provider failed. 

Expected results:
Running the pytest with nm provider should not failed.
Comment 7 Rich Megginson 2022-04-27 22:49:01 UTC 

*** This bug has been marked as a duplicate of bug 2065217 ***