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.
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, 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-2020:1696
Description of problem: fail to add ovs-bridge when vlan-mode is presented in yaml Version-Release number of selected component (if applicable): nmstate-0.0.7-1.el8.noarch How reproducible: Always Steps to Reproduce: add ovs with following yaml: --- interfaces: - name: ovs1 type: ovs-interface state: up ipv4: enabled: true address: - ip: 192.0.3.1 prefix-length: 24 - name: ovs0 type: ovs-interface state: up ipv4: enabled: true address: - ip: 192.0.2.1 prefix-length: 24 mac-address: 32:e2:7b:45:f8:98 mtu: 1400 - name: ovs-br0 type: ovs-bridge state: up bridge: options: fail-mode: '' mcast-snooping-enable: false rstp: false stp: true port: - name: ovs0 type: internal vlan-mode: access access-tag: 2 - name: ovs1 type: internal Actual results: [root@kvm-01-guest23 ovs]# nmstatectl set ovs-vlan-mode.yaml Traceback (most recent call last): File "/usr/bin/nmstatectl", line 11, in <module> load_entry_point('nmstate==0.0.7', 'console_scripts', 'nmstatectl')() File "/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 59, in main return args.func(args) File "/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 187, in apply args.timeout) File "/usr/lib/python3.6/site-packages/nmstatectl/nmstatectl.py", line 206, in apply_state checkpoint = libnmstate.apply(state, verify_change, commit, timeout) File "/usr/lib/python3.6/site-packages/libnmstate/netapplier.py", line 53, in apply validator.validate(desired_state) File "/usr/lib/python3.6/site-packages/libnmstate/validator.py", line 33, in validate js.validate(data, validation_schema) File "/usr/lib/python3.6/site-packages/jsonschema/validators.py", line 541, in validate cls(schema, *args, **kwargs).validate(instance) File "/usr/lib/python3.6/site-packages/jsonschema/validators.py", line 130, in validate raise error jsonschema.exceptions.ValidationError: {'name': 'ovs-br0', 'type': 'ovs-bridge', 'state': 'up', 'bridge': {'options': {'fail-mode': '', 'mcast-snooping-enable': False, 'rstp': False, 'stp': True}, 'port': [{'name': 'ovs0', 'type': 'internal', 'vlan-mode': 'access', 'access-tag': 2}, {'name': 'ovs1', 'type': 'internal'}]}} is not valid under any of the given schemas Failed validating 'oneOf' in schema['properties']['interfaces']['items']['allOf'][3]: {'oneOf': [{'$ref': '#/definitions/interface-unknown/rw'}, {'$ref': '#/definitions/interface-ethernet/rw'}, {'$ref': '#/definitions/interface-bond/rw'}, {'$ref': '#/definitions/interface-linux-bridge/rw'}, {'$ref': '#/definitions/interface-ovs-bridge/all'}, {'$ref': '#/definitions/interface-ovs-interface/rw'}, {'$ref': '#/definitions/interface-dummy/rw'}, {'$ref': '#/definitions/interface-vlan/rw'}]} On instance['interfaces'][2]: {'bridge': {'options': {'fail-mode': '', 'mcast-snooping-enable': False, 'rstp': False, 'stp': True}, 'port': [{'access-tag': 2, 'name': 'ovs0', 'type': 'internal', 'vlan-mode': 'access'}, {'name': 'ovs1', 'type': 'internal'}]}, 'name': 'ovs-br0', 'state': 'up', 'type': 'ovs-bridge'} Expected results: no error Additional info: