-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
nmstate-2.2.32-1.el9
-
None
-
Moderate
-
ZStream
-
rhel-sst-network-management
-
ssg_networking
-
2
-
False
-
-
None
-
None
-
Approved Blocker
-
-
Pass
-
None
-
None
Description of problem:
When deploying cluster or updating cluster network via nmstate the vlan.flags are not as expected. This flag causes the vlan tag to show up on pods using the interface. Expected behavior is no tag at pod. Expected: < vlan.flags: 1 (REORDER_HEADERS) Via nmstate: > vlan.flags: 0 (NONE)
Version-Release number of selected component (if applicable):
How reproducible:
Always, this is the default behavior of nmstate
Steps to Reproduce:
1. Deploy cluster with vlan interface or create new interface via nmstate operater 2. View con vlan.flags, "nmcli con show <intefaceName> |grep vlan.flags" 3. Manually create a new vlan inteface via nmtui 4. Observe differences between of vlan.flags using both methods.
Actual results:
vlan.flags: 0 (NONE)
Expected results:
vlan.flags: 1 (REORDER_HEADERS)
Additional info:
- is duplicated by
-
RHEL-27843 Ansible RHEL network system role issue with nmstate (vlan.flags = NONE)
- Closed
- links to
-
RHBA-2024:129019 nmstate bug fix and enhancement update