Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-105975

Failed to create ovn mapping if ovs bridges don't exist

Linking RHIVOS CVEs to...Migration: Automation ...SWIFT: POC ConversionSync from "Extern...XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • rhel-9.7
    • nmstate
    • None
    • Yes
    • None
    • rhel-net-mgmt
    • None
    • False
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Hide

      Definition of Done:

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.

      None

      ( ) Integration test case is available upstream.

      ( ) Code is reviewed and merged upstream.

      ( ) Preliminary testing is done.

      ( ) Upstream documentation is written in the upstream MR.

      ( ) Release notes text is written in the RHEL issue.

      ( ) A demo is recorded

      Show
      Definition of Done: Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. None ( ) Integration test case is available upstream. ( ) Code is reviewed and merged upstream. ( ) Preliminary testing is done. ( ) Upstream documentation is written in the upstream MR. ( ) Release notes text is written in the RHEL issue. ( ) A demo is recorded
    • None
    • None
    • Unspecified
    • Unspecified
    • Unspecified
    • None

      What were you trying to do that didn't work?

      A regression test of Bug 2209690 - RFE - bridge mapping API for OVS

      It works well in nmstate-2.2.46-1 and lower versions, now failed in nmstate-2.2.48-1

       

      If the target ovs bridges exist, it works well; but in 2.2.46-1 it doesn't require so, need to check if the behaviour in 2.2.48-1 is ok.

       

      What is the impact of this issue to you?

      Please provide the package NVR for which the bug is seen:

      nmstate-2.2.48-1.el9.x86_64
      NetworkManager-1.53.92-1.el9.x86_64
      openvswitch3.1-3.1.7-163.el9fdp.x86_64

      How reproducible is this bug?:

      100%

      Steps to reproduce

       

      cat << EOF > expected-fail-bridge-mapping.yaml
ovs-db:
  external_ids:
    ovn-bridge-mappings: yellow:ovsbr0
    key0: value0
ovn:
  bridge-mappings:
  - localnet: local0
    bridge: ovsbr0
    state: present
  - localnet: local1
    bridge: ovsbr1
EOF

cat << EOF > unexpected-fail-bridge-mapping.yaml
ovs-db:
  external_ids:
    key0: value0
ovn:
  bridge-mappings:
  - localnet: local0
    bridge: ovsbr0
    state: present
  - localnet: local1
    bridge: ovsbr1
EOF


nmstatectl apply expected-fail-bridge-mapping.yaml # expected failed in both nmstate-2.2.46-1 and 2.2.48-1

nmstatectl apply unexpected-fail-bridge-mapping.yaml # failed in 2.2.48-1 only

       

      Expected results

      The 2nd apply should pass

      Actual results

      Both got

      [21:40:35@vm-10-0-187-98 ~]0# nmstatectl apply expected-fail-bridge-mapping.yaml
[2025-07-28T13:40:41Z INFO  nmstatectl] Nmstate version: 2.2.48
NmstateError: InvalidArgument: There is no OVS bridge holding name desired by OVN bridge ovsbr0 localnet local0
[21:40:41@vm-10-0-187-98 ~]1# nmstatectl apply unexpected-fail-bridge-mapping.yaml
[2025-07-28T13:40:51Z INFO  nmstatectl] Nmstate version: 2.2.48
NmstateError: InvalidArgument: There is no OVS bridge holding name desired by OVN bridge ovsbr0 localnet local0

              nm-team Network Management Team
              rh-ee-mshi1 Mingyu Shi
              Network Management Team Network Management Team
              Mingyu Shi Mingyu Shi
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: