Bug 1686634 - Virtual devices fail to activate after failing to realize the device once
Summary: Virtual devices fail to activate after failing to realize the device once
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 8.0
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-07 22:38 UTC by Thomas Haller
Modified: 2019-12-06 09:37 UTC (History)
8 users (show)

Fixed In Version: NetworkManager-1.22.0-0.2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

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 4 Vladimir Benes 2019-12-06 09:37:56 UTC
bond_reconnect_previously_unavailable_device added.


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