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:
OVN uses an OpenVSwitch bridge named br-int to connect its ports and do its have all its smart openflow rules. br-int is created and soly controlled by OVN. br-int can delegate its outgoing traffic either to a tunnel device, or to a simple-stupid OpenVSwitch bridge, e.g. brbond0, connected to a bonding device.

The administrator of the host is responsible to create the latter bridge and connect it to the proper interface.

In this RFE I am asking to let NM define such an interface. Just like NM is able to create a Linux bridge and connect it to an underlying connection, it should do the same for an OVS bridge.

Just like it can set an IP address on a Linux bridge, I'm requesting to create a port on a the OVS bridge, and configure the address there.

RHV does the latter on itself, but I believe that it would be better to implement this once, on the platform level.

Note that unlike Linux bond, OVS does not need to be connected through a vlan device in order to tag all outgoing traffic. A better implementation would be to vlan-tag the underlying interface within the OVS bridge.

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=79168a54344f8fb72fda88bf02bce908d2ce3f31

This should work but it doesn't:
nmcli conn add conn.type ovs-bridge conn.interface bridge0
nmcli conn add conn.type ovs-port conn.interface port1 conn.master bridge0
nmcli conn add type ethernet conn.interface eth2 conn.master port1 slave-type ovs-port

it works with dummy device:
nmcli conn add conn.type ovs-bridge conn.interface bridge0
nmcli conn add conn.type ovs-port conn.interface port1 conn.master bridge0
nmcli conn add type dummy conn.interface dummy0 conn.master port1 slave-type ovs-port

moving back to ON_QA as it looks blocking bug is fixed: bug 1519179

few bugs filed but generally working well, automated and running in CI.

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-2018:0778

On rhel-8.0, this is solved by just dropping the "Requires: openvswitch".
See bug 1629178.

This bug is already added to Errata and is in status CLOSED. If you think that something needs to be fixed for rhel-7.y, please create a new bug.