Hide Forgot
Description of problem: At an openshift 4.8 cluster with OVNKubernetes after creating a veth it's impossible to add the peer to the br-ex bridge, only the veth is added and the rest of interfaces are deleted. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. git clone https://github.com/nmstate/nmstate && cd nmstate 2. export KUBEVIRT_PROVIDER=external 3. export KUBECONFIG=[path to the kubeconfig] 4. ./automation.sh --k8s --centos-stream --test-type=none --debug-shell 5. [different shell] oc cp -n nmstate state.yaml conformance:/tmp/ 6. nmstatectl set /tmp/state.yaml Actual results: name: br-ex type: ovs-bridge state: up bridge: options: fail-mode: '' mcast-snooping-enable: false rstp: false stp: false port: - name: ovn-veth lldp: enabled: false Expected results: name: br-ex type: ovs-bridge state: up bridge: options: fail-mode: '' mcast-snooping-enable: false rstp: false stp: false port: - name: br-ex - name: enp5s0 - name: ovn-veth lldp: enabled: false Additional info:
Created attachment 1786758 [details] Desired state
Created attachment 1786759 [details] Full logs after nmstatectl set
Created attachment 1786760 [details] Full logs after nmstatectl show
Add enp5s0 to the desired state improves things a little since it appears as part of the ports, but if I add the br-ex ovs-interface br-ex ovs-bridge breaks.
Hi Quique, thanks for this report. I am looking into this.
Verified with versions: nmstate-1.1.0-3.el8.noarch nispor-1.1.1-1.el8.x86_64 NetworkManager-1.32.10-1.el8.x86_64 openvswitch2.13-2.13.0-116.el8fdp.x86_64 [14:03:54@ibm-x3650m4-01-vm-05 ~]0# ip link add enp5s0 type veth [14:03:57@ibm-x3650m4-01-vm-05 ~]0# nmcli dev set enp5s0 managed yes [14:03:57@ibm-x3650m4-01-vm-05 ~]0# [14:03:57@ibm-x3650m4-01-vm-05 ~]0# echo " > interfaces: > - name: br-ex > type: ovs-bridge > state: up > bridge: > options: > fail-mode: '' > mcast-snooping-enable: false > rstp: false > stp: false > port: > - name: br-ex > - name: enp5s0 > " | nmstatectl set /tmp/nmstatelog/2021-08-24-14:03:57-722645120.log Desired state applied: --- interfaces: - name: br-ex type: ovs-bridge state: up bridge: options: fail-mode: '' mcast-snooping-enable: false rstp: false stp: false port: - name: br-ex - name: enp5s0 /tmp/nmstatelog/2021-08-24-14:03:57-722645120.0.log nmstatectl set return 0 [14:03:59@ibm-x3650m4-01-vm-05 ~]0# [14:03:59@ibm-x3650m4-01-vm-05 ~]0# echo " > interfaces: > - name: br-ex > type: ovs-bridge > state: up > bridge: > options: > fail-mode: '' > mcast-snooping-enable: false > rstp: false > stp: false > port: > - name: br-ex > - name: enp5s0 > - name: ovn-veth > lldp: > enabled: false > - ipv4: > enabled: false > dhcp: false > ipv6: > enabled: false > autoconf: false > dhcp: false > name: cnv-veth > state: up > type: veth > veth: > peer: ovn-veth > - ipv4: > enabled: false > dhcp: false > ipv6: > enabled: false > autoconf: false > dhcp: false > name: ovn-veth > state: up > type: veth > veth: > peer: cnv-veth > " | nmstatectl set /tmp/nmstatelog/2021-08-24-14:04:02-674235659.log Desired state applied: --- interfaces: - name: br-ex type: ovs-bridge state: up bridge: options: fail-mode: '' mcast-snooping-enable: false rstp: false stp: false port: - name: br-ex - name: enp5s0 - name: ovn-veth lldp: enabled: false - name: cnv-veth type: veth state: up ipv4: enabled: false dhcp: false ipv6: enabled: false autoconf: false dhcp: false veth: peer: ovn-veth - name: ovn-veth type: veth state: up ipv4: enabled: false dhcp: false ipv6: enabled: false autoconf: false dhcp: false veth: peer: cnv-veth /tmp/nmstatelog/2021-08-24-14:04:02-674235659.0.log nmstatectl set return 0
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 (nmstate bug fix and enhancement update), 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-2021:4157