-
Bug
-
Resolution: Done
-
Undefined
-
4.17.z, 4.16.z, 4.18.z, 4.19.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
3
-
Moderate
-
None
-
None
-
None
-
None
-
OSDOCS Sprint 275
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Certain interface and bridge names are reserved for internal OpenShift usage and cannot be used for customized NMstate bridges.
# ignore known SDN-managed devices
[device]
match-device=interface-name:br-int;interface-name:br-local;interface-name:br-nexthop;interface-name:ovn-k8s-*;interface-name:k8s-*;interface-name:tun0;interface-name:br0;interface-name:patch-br-*;interface-name:br-ext;interface-name:ext-vxlan;interface-name:ext;interface-name:int;interface-name:vxlan_sys_*;interface-name:genev_sys_*;driver:veth
managed=0
These interfaces are "unmanaged" by NetworkManage, so NMstate cannot create or destroy them.
Version-Release number of selected component (if applicable):
4.16.38
How reproducible:
Always
Steps to Reproduce:
1. Attempt to create a new bridge with NMstate using one of the reserved names
2.
interfaces:
- name: br0
type: ovs-interface
state: up
ipv4:
enabled: true
dhcp: true
3.
Actual results:
[2025-06-17T14:12:25Z INFO nmstate::query_apply::net_state] Retrying on: VerificationError: Absent/Down interface br0/ovs-interface still found as OvsInterface(OvsInterface { base: BaseInterface { name: "br0", profile_name: None, description: None, iface_type: OvsInterface, driver: None, state: Ignore
Note the state: Ignore
Expected results:
Documentation warning not to use the reserved names.
- clones
-
-
- Closed
-
- links to