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.
I have a problem with the Interface external_ids:iface-id property in OVN
To configure an ovs port on the host for OVN, you need to set the value of
this property to the name of the Logical-Switch-Port from the NorthDB:
ovs-vsctl add-port br-int lport1 -- set Interface lport1 external_ids:iface-id=sw0-port1
This is using the name, not the id.
Specifying the id does not work.
This is ok when you do it by hand, but is inconvenient when you try to
automate it.
Libvirt offers a chance to automate deployment of ovs connected nics, but it
only accepts an UUID value, so using the name makes this impossible.
Would it be possible for OVN to interpret both values (I realize this
would cause some issues)?
For reference, the way to set this in libvirt xml:
<interface>
...
<virtualport type='openvswitch'>
<parameters interfaceid='lsp-name'/>
</virtualport>
Using the name results in:
libvirtError: XML error: cannot parse interfaceid parameter as a uuid
Another disadvantage is that this forces the LSP name to be unique,
unlike for example Logical-Switch names, which can be duplicated.
We have a workaround, but it causes some unneccessary complications.
I have a problem with the Interface external_ids:iface-id property in OVN To configure an ovs port on the host for OVN, you need to set the value of this property to the name of the Logical-Switch-Port from the NorthDB: ovs-vsctl add-port br-int lport1 -- set Interface lport1 external_ids:iface-id=sw0-port1 This is using the name, not the id. Specifying the id does not work. This is ok when you do it by hand, but is inconvenient when you try to automate it. Libvirt offers a chance to automate deployment of ovs connected nics, but it only accepts an UUID value, so using the name makes this impossible. Would it be possible for OVN to interpret both values (I realize this would cause some issues)? For reference, the way to set this in libvirt xml: <interface> ... <virtualport type='openvswitch'> <parameters interfaceid='lsp-name'/> </virtualport> Using the name results in: libvirtError: XML error: cannot parse interfaceid parameter as a uuid Another disadvantage is that this forces the LSP name to be unique, unlike for example Logical-Switch names, which can be duplicated. We have a workaround, but it causes some unneccessary complications.