Bug 1462741 - NM manages veth interfaces when ethtool is missing and predictable names are disabled
NM manages veth interfaces when ethtool is missing and predictable names are ...
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: sushil kulkarni
Desktop QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-19 08:46 EDT by Beniamino Galvani
Modified: 2017-07-13 12:13 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-07-13 12:13:42 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Beniamino Galvani 2017-06-19 08:46:34 EDT
Description of problem:

When ethtool is not installed and the udev rule
"80-net-setup-link.rules" is masked (i.e. predictable interface names
are disabled), ID_NET_DRIVER is unset and the rule
"84-nm-drivers.rules" fails to detect the driver. Therefore, all
interfaces are managed by NM, including veths which should not be
managed.

This happens, for example, on RHEL atomic host images.

The NetworkManager package should probably have a dependency on ethtool.
Comment 3 Thomas Haller 2017-06-19 09:54:15 EDT
I think "80-net-setup-link.rules" does a lot of setup for net-devices. Disabling it seems like a bad idea, and it would be expected to break other stuff.

Although various sources on the internet suggest to mask 80-net-setup-link.rules,  the better way to configure the naming scheme is a .link file with "[Link] NamePolicy=".

This seems like a bug in atomic host, whoever masks 80-net-setup-link.rules.



Almost no packages require "ethtool", and NM doesn't need it either -- except for unusual cases like the present bug.

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