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
# 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):
nmstate does not have the implementation of ovs-port so there is no concept of bonding two interfaces into it.
Approved upstream: https://github.com/nmstate/nmstate/pull/795
Example of OVS bond:
- name: ovs-br0
- name: ovs-bond1
- name: eth1
- name: eth2
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.