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.
Description of problem:
Currently nmstate doesn't suepport reating an OVS bridge, with a VLAN port in trunk mode and trunk-tags range.
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux CoreOS 411.86.202207150124-0
RHEL 8.6
NetworkManager (on cluster worker node): 1.36.0-7.el8_6
NetworkManager (on nmstate-handler pod): 1.36.0-7.el8_6
nmstate (on nmstate-handler pod): nmstate-1.2.1-3.el8_6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Create an OVS bridge with a VLAN port in trunk mode and trunk-tags range.
I used the following policy to achieve that:
apiVersion: nmstate.io/v1
kind: NodeNetworkConfigurationPolicy
metadata:
name: ovs-bridge-policy
spec:
desiredState:
interfaces:
- bridge:
options:
stp: false
port:
- name: eno4
vlan:
mode: trunk
trunk-tags:
- id-range:
max: 1019
min: 1000
name: br1test
state: up
type: ovs-bridge
nodeSelector:
node-role.kubernetes.io/worker: ""
(Modify port name and VLAN id-range per according to your environment).
Actual results:
The configuration fails to configure after timeout:
$ oc get nncp -w
NAME STATUS REASON
ovs-bridge-policy Progressing ConfigurationProgressing
ovs-bridge-policy Progressing ConfigurationProgressing
ovs-bridge-policy Degraded FailedToConfigure
Expected results:
Successful configuration.
Additional info:
1. This configuration is not supported in NetworkManager as well (not only in nmstate).
2. The same configuration succeeds when the bridge type is linux-bridge, i.e.
apiVersion: nmstate.io/v1
kind: NodeNetworkConfigurationPolicy
metadata:
name: linux-bridge-policy
spec:
desiredState:
interfaces:
- bridge:
options:
stp: false
port:
- name: eno4
vlan:
mode: trunk
trunk-tags:
- id-range:
max: 1019
min: 1000
name: br1test
state: up
type: linux-bridge
nodeSelector:
node-role.kubernetes.io/worker: ""
3. The same configuration (OVS bridge) succeeds, with a VLAN port in access mode and an explicit ID tag, i.e.
apiVersion: nmstate.io/v1
kind: NodeNetworkConfigurationPolicy
metadata:
name: ovs-bridge-policy
spec:
desiredState:
interfaces:
- bridge:
options:
stp: false
port:
- name: eno4
vlan:
mode: access
tag: 1021
name: br1test
state: up
type: ovs-bridge
nodeSelector:
node-role.kubernetes.io/worker: ""
4. This was found on RHEL 8.6, however it can be targeted to RHEL 9.
This require support from NetworkManager also.
According to manpage of `ovs-vswitchd.conf.db`, we can use `trunks` property which can hold up to 4096 integers in range of 0 - 4095.
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-2023:2190
Description of problem: Currently nmstate doesn't suepport reating an OVS bridge, with a VLAN port in trunk mode and trunk-tags range. Version-Release number of selected component (if applicable): Red Hat Enterprise Linux CoreOS 411.86.202207150124-0 RHEL 8.6 NetworkManager (on cluster worker node): 1.36.0-7.el8_6 NetworkManager (on nmstate-handler pod): 1.36.0-7.el8_6 nmstate (on nmstate-handler pod): nmstate-1.2.1-3.el8_6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create an OVS bridge with a VLAN port in trunk mode and trunk-tags range. I used the following policy to achieve that: apiVersion: nmstate.io/v1 kind: NodeNetworkConfigurationPolicy metadata: name: ovs-bridge-policy spec: desiredState: interfaces: - bridge: options: stp: false port: - name: eno4 vlan: mode: trunk trunk-tags: - id-range: max: 1019 min: 1000 name: br1test state: up type: ovs-bridge nodeSelector: node-role.kubernetes.io/worker: "" (Modify port name and VLAN id-range per according to your environment). Actual results: The configuration fails to configure after timeout: $ oc get nncp -w NAME STATUS REASON ovs-bridge-policy Progressing ConfigurationProgressing ovs-bridge-policy Progressing ConfigurationProgressing ovs-bridge-policy Degraded FailedToConfigure Expected results: Successful configuration. Additional info: 1. This configuration is not supported in NetworkManager as well (not only in nmstate). 2. The same configuration succeeds when the bridge type is linux-bridge, i.e. apiVersion: nmstate.io/v1 kind: NodeNetworkConfigurationPolicy metadata: name: linux-bridge-policy spec: desiredState: interfaces: - bridge: options: stp: false port: - name: eno4 vlan: mode: trunk trunk-tags: - id-range: max: 1019 min: 1000 name: br1test state: up type: linux-bridge nodeSelector: node-role.kubernetes.io/worker: "" 3. The same configuration (OVS bridge) succeeds, with a VLAN port in access mode and an explicit ID tag, i.e. apiVersion: nmstate.io/v1 kind: NodeNetworkConfigurationPolicy metadata: name: ovs-bridge-policy spec: desiredState: interfaces: - bridge: options: stp: false port: - name: eno4 vlan: mode: access tag: 1021 name: br1test state: up type: ovs-bridge nodeSelector: node-role.kubernetes.io/worker: "" 4. This was found on RHEL 8.6, however it can be targeted to RHEL 9.