Bug 1686634

Summary: Virtual devices fail to activate after failing to realize the device once
Product: Red Hat Enterprise Linux 8 Reporter: Thomas Haller <thaller>
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 8.0CC: atragler, bgalvani, fgiudici, lrintel, rkhan, sukulkar, thaller, vbenes
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.22.0-0.2.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 16:52:36 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:

Description Thomas Haller 2019-03-07 22:38:38 UTC 
This applies to software devices in general.


For example, with WireGuard...

- if you first don't have the WireGuard kernel module installed
- then create a profile that causes NetworkManager to try to connect (which fails, as the device cannot be created/realized)
- then install the WireGuard kernel module
- then activation of the device still fails



But let's instead reproduce it with bond:


<<<<<

# ensure you have no NetworkManager connection profiles for bonds

rmmod bonding
echo "blacklist bonding" > /etc/modprobe.d/no-bonding.conf

# verify it works.
modprobe --use-blacklist bonding


# create a profile, which will try to autoconnect...
nmcli connection add type bond con-name b0


# of course, autoconnect failed. Note in the log:
# <warn>  [1551997903.2151] platform-linux: do-add-link[nm-bond/bond]: failure # <error> [1551997903.2152] manager: (b0) couldn't create the device: Failed to create bond interface 'nm-bond' for 'b0': Operation not supported


# now, enable and load the module again

rm -f /etc/modprobe.d/no-bonding.conf
modprobe bonding


# Note that NM fails to activate the profile:

nmcli connection up b0
#Error: Connection activation failed: Failed to find a compatible device for this connection



# note that deleting the bonding profile, and recreating it would succeed to activate it.

<<<<<<
Comment 1 Beniamino Galvani 2019-08-30 13:00:58 UTC 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/252
Comment 2 Beniamino Galvani 2019-09-04 07:24:35 UTC 
Fixed by

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/dbfbbed53c989aa7b7ac88ad8292e205c6ae0271
Comment 4 Vladimir Benes 2019-12-06 09:37:56 UTC 
bond_reconnect_previously_unavailable_device added.
Comment 6 errata-xmlrpc 2020-04-28 16:52:36 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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1847