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.

Bug 1964307

Summary: Impossible to add a OVS bridge port
Product: Red Hat Enterprise Linux 8 Reporter: Quique Llorente <ellorent>
Component: nmstateAssignee: Fernando F. Mancera <ferferna>
Status: CLOSED ERRATA QA Contact: Mingyu Shi <mshi>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 8.4CC: ferferna, fge, jiji, jishi, network-qe, phoracek, till
Target Milestone: betaKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: nmstate-1.1.0-3.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-09 17:43:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1885605    
Attachments:
Description Flags
Desired state
none
Full logs after nmstatectl set
none
Full logs after nmstatectl show none

Description Quique Llorente 2021-05-25 07:36:03 UTC 
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:
Comment 1 Quique Llorente 2021-05-25 07:37:12 UTC 
Created attachment 1786758 [details]
Desired state
Comment 2 Quique Llorente 2021-05-25 07:38:20 UTC 
Created attachment 1786759 [details]
Full logs after nmstatectl set
Comment 3 Quique Llorente 2021-05-25 07:39:37 UTC 
Created attachment 1786760 [details]
Full logs after nmstatectl show
Comment 4 Quique Llorente 2021-05-25 13:29:43 UTC 
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.
Comment 5 Fernando F. Mancera 2021-06-08 22:48:02 UTC 
Hi Quique, thanks for this report. I am looking into this.
Comment 11 Mingyu Shi 2021-08-24 06:05:36 UTC 
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
Comment 13 errata-xmlrpc 2021-11-09 17:43:51 UTC 
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