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.
Description of problem:
By default, NetworkManager mark veth interface as unmanaged,
After a profile/connection been created with `connection.interface-name` targeting the unmanaged veth interface, the
`NMClient.activate_connection_async()` call will fail with no suitable
interface found.
Version-Release number of selected component (if applicable):
NetworkManager-1.20.0-3.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
1. sudo ip link add eth1 type veth peer name eth1.ep
2. sudo nmstatectl edit eth1
3. Change the 'state: down' to 'state: up'
Actual results:
2019-11-14 20:41:46,529 root ERROR NM main-loop aborted: Connection activation failed on device eth1: error=nm-manager-error-quark: The device 'eth1' has no connections available for activation. (2)
Expected results:
eth1(veth) become managed by NetworkManager and profile/connection been activated.
Additional info:
The nmcli does not have this problem as it changes the device to managed
state before activation.
Not sure related or not.
When has NM config like:
```
[device]
match-device=*
managed=0
```
At the boot stage, NM does not activate any interfaces even their profiles is `connection.autoconnect: yes`
Base on feedback from NetworkManager team, when explicitly activate a profile, the device should became managed automaticlly,
this is what this bug requesting.
As workaround in nmstate, we use `NM.Device.set_managed()` which has race issue. The documented `NM.Device.set_managed_async()`
does not exist in NM 1.22 release.
(In reply to Gris Ge from comment #5)
> As workaround in nmstate, we use `NM.Device.set_managed()` which has race
> issue. The documented `NM.Device.set_managed_async()`
> does not exist in NM 1.22 release.
Is the race the problem that the cache is not updated after calling `NM.Device.set_managed()`? Possible workarounds for this are
- iterate the mainloop after calling it (assumed to fixing this)
- Directly use dbus to change the state using g_dbus_connection_call() inside the mainloop