Description of problem:
For info upstream in https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/509
In short, let's not default to generating connection profiles that attempt DHCP if there is a vlan device on top.
Version-Release number of selected component (if applicable):
NetworkManager-1.22.8-6.el8_2.x86_64
How reproducible:
Always
Steps to Reproduce:
See upstream bug
Actual results:
bond0 gets attempted for DHCP when there is a bond0.100. If bond0 can't get DHCP then the VLAN device (bond0.100) gets taken down (see bz#1900038).
Expected results:
bond0 doesn't attempt DHCP or DHCP6
Additional info:
The upstream bug has been fixed upstream.
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 (Moderate: NetworkManager and libnma security, bug fix, and enhancement update), 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/RHSA-2021:1574