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.
DescriptionQuique Llorente
2019-07-16 13:51:26 UTC
Created attachment 1591053[details]
ovs bridge configuration script for customer0
Description of problem:
CNV team needs to configure ovs-bridge with a bonding port for customer0
The steps usin nmcli are the following:
## change these to match your hosts
default_device=em1
secondary_device=em3
# make bridge
nmcli conn add type ovs-bridge conn.interface brcnv
nmcli conn add type ovs-port conn.interface port0 master brcnv
nmcli conn add type ovs-port conn.interface brcnv-port master brcnv
nmcli conn add type ovs-interface conn.id brcnv-iface conn.interface brcnv master brcnv-port ipv4.method auto
# make bond
nmcli conn add type ovs-port conn.interface bond0 master brcnv ovs-port.bond-mode balance-slb
nmcli conn add type ethernet conn.interface \$default_device master bond0
nmcli conn add type ethernet conn.interface \$secondary_device master bond0
Version-Release number of selected component (if applicable):
nmsate v0.7.0
How reproducible:
nmstate does not have the implementation of ovs-port so there is no concept of bonding two interfaces into it.
Expected results:
Additional info:
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:1696
Created attachment 1591053 [details] ovs bridge configuration script for customer0 Description of problem: CNV team needs to configure ovs-bridge with a bonding port for customer0 The steps usin nmcli are the following: ## change these to match your hosts default_device=em1 secondary_device=em3 # make bridge nmcli conn add type ovs-bridge conn.interface brcnv nmcli conn add type ovs-port conn.interface port0 master brcnv nmcli conn add type ovs-port conn.interface brcnv-port master brcnv nmcli conn add type ovs-interface conn.id brcnv-iface conn.interface brcnv master brcnv-port ipv4.method auto # make bond nmcli conn add type ovs-port conn.interface bond0 master brcnv ovs-port.bond-mode balance-slb nmcli conn add type ethernet conn.interface \$default_device master bond0 nmcli conn add type ethernet conn.interface \$secondary_device master bond0 Version-Release number of selected component (if applicable): nmsate v0.7.0 How reproducible: nmstate does not have the implementation of ovs-port so there is no concept of bonding two interfaces into it. Expected results: Additional info: