-
Story
-
Resolution: Done-Errata
-
Normal
-
None
-
nmstate-2.2.48-1.el9
-
None
-
rhel-net-mgmt
-
ssg_networking
-
1
-
False
-
False
-
-
None
-
None
-
-
Requested
-
Automated
-
None
Goal
- As a user, I would like to prevent myself from making simple, but breaking mistakes, by having OVN validate that my bridge mapping is valid before applying it.
Acceptance Criteria
If try to apply an nmsate config that tries to map a localnet to a bridge that doesn't exist, nmstate should fail the config and not apply it.
For example this should apply successfully, because the localnet, vlan-99 is mapped to a bridge that exists, ovs-br0 (OCP NNCP example):
spec: nodeSelector: node-role.kubernetes.io/worker: '' desiredState: interfaces: - name: ovs-br0 type: ovs-bridge state: up bridge: options: stp: true port: - name: eno4 ovn: bridge-mappings: - localnet: vlan-99 bridge: ovs-br0 state: present
This example should fail, because ovs-br12345 does not exist (OCP NNCP example):
spec: nodeSelector: node-role.kubernetes.io/worker: '' desiredState: interfaces: - name: ovs-br0 type: ovs-bridge state: up bridge: options: stp: true port: - name: eno4 ovn: bridge-mappings: - localnet: vlan-99 bridge: ovs-br12345 state: present
- clones
-
RHEL-37922 Provide validation of OVN Bridge Mapping before applying
-
- Closed
-
- links to
-
RHBA-2025:146752
nmstate bug fix and enhancement update