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.

Created attachment 1745535 [details]
Reproduce script

Description of problem:

When both bond interface and OVS port profile are using the same `bond0` as
`connection.interface-name`, cannot create VLAN over bond.


Version-Release number of selected component (if applicable):
NetworkManager-1.30.0-0.5.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. sudo ./bug.sh
2.
3.

Actual results:

Error: Connection activation failed: bond0.100 failed to create resources: cannot retrieve ifindex of interface bond0 (Open vSwitch Port)

Expected results:

VLAN created from kernel bond0 interface.

Additional info:

The OVS bridge and OVS port are user space only interface, VLAN should not
use them as parent.

The script creates an OVS bond named 'bond0' and then a Linux bond
with the same name. It also creates a VLAN with parent 'bond0';
however this is ambiguous because there are two interfaces with the
same name. In such cases it is possible to specify a connection UUID
as parent.

Yes, NM could be smarter and exclude the OVS bond because it doesn't
have a kernel link and therefore it can't be used a parent for the
VLAN. At the moment this doesn't happen because the code to look up
the parent is completely generic and doesn't care about device
types. Perhaps this can be improved.

Thanks for the info. I will use UUID as workaround in nmstate.

You may take this as low priority or even close as won't fix.

Gris, does that mean that we would be able to create a VLAN using nmstate over a bonding attached to an OVS bridge with your workaround?

(In reply to Petr Horáček from comment #3)
> Gris, does that mean that we would be able to create a VLAN using nmstate
> over a bonding attached to an OVS bridge with your workaround?

Yes. I am working on that.