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:
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
cat > 'reproduce_nmcli_vlan_autoconnect_bug.sh' <<EOF
parent_interface=tst83
vlan_interface="${parent_interface}.101"
ip link show "${parent_interface}" &>/dev/null || ip link add "${parent_interface}" type veth peer "peer${parent_interface}"
parent_uuid="$(nmcli con add type ethernet ifname "${parent_interface}" con-name "${parent_interface}" ipv4.method disabled ipv6.method ignore autoconnect yes | cut -d '(' -f 2 | cut -d ')' -f 1)"
nmcli con add type vlan ifname "${vlan_interface}" dev "${parent_uuid}" id 101 autoconnect yes connection.id "${vlan_interface}"
systemctl restart NetworkManager
nmcli con up "${vlan_interface}"
exit 0
# cleanup:
nmcli con del "${parent_interface}" "${vlan_interface}"; nmcli dev delete "${parent_interface}"
EOF
bash reproduce_nmcli_vlan_autoconnect_bug.sh
Actual results:
Failed to find a compatible device for this connection
Expected results:
Should activate the connection
Additional info:
Using the interface name instead of the UUID works.
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:1162
Description of problem: Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: cat > 'reproduce_nmcli_vlan_autoconnect_bug.sh' <<EOF parent_interface=tst83 vlan_interface="${parent_interface}.101" ip link show "${parent_interface}" &>/dev/null || ip link add "${parent_interface}" type veth peer "peer${parent_interface}" parent_uuid="$(nmcli con add type ethernet ifname "${parent_interface}" con-name "${parent_interface}" ipv4.method disabled ipv6.method ignore autoconnect yes | cut -d '(' -f 2 | cut -d ')' -f 1)" nmcli con add type vlan ifname "${vlan_interface}" dev "${parent_uuid}" id 101 autoconnect yes connection.id "${vlan_interface}" systemctl restart NetworkManager nmcli con up "${vlan_interface}" exit 0 # cleanup: nmcli con del "${parent_interface}" "${vlan_interface}"; nmcli dev delete "${parent_interface}" EOF bash reproduce_nmcli_vlan_autoconnect_bug.sh Actual results: Failed to find a compatible device for this connection Expected results: Should activate the connection Additional info: Using the interface name instead of the UUID works.