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:
Some failure reasons and return values are different between rust and python version.
Version-Release number of selected component (if applicable):
nmstate-2.1.1-0.alpha.20220519.437e4a9.el9.x86_64
How reproducible:
Steps to Reproduce:
For example, when using "nmstatectl apply" such a state in command line:
interfaces:
- name: br0
type: linux-bridge
state: up
bridge:
options:
stp:
enabled: true
port:
- name: veth0
vlan:
mode: trunk
tag: 200
trunk-tags:
- id-range:
min: 600
max: 900
- id: 800
- id-range:
max: 500
min: 400
- name: veth1
vlan:
mode: trunk
tag: 200
trunk-tags:
- id-range:
min: 600
max: 900
- id: 800
- id-range:
max: 500
min: 400
ipv4:
enabled: true
dhcp: true
ipv6:
enabled: true
autoconf: true
dhcp: true
Actual results:
RHEL 9.1 returns value 65, with error:
NmstateError: Bug: DbusConnectionError: org.freedesktop.NetworkManager.Settings.Connection.InvalidProperty: bridge-port.vlans: duplicate bridge VLAN vid 800 dbus: Some(MethodError("org.freedesktop.NetworkManager.Settings.Connection.InvalidProperty", Some("bridge-port.vlans: duplicate bridge VLAN vid 800"), Msg { type: Error, sender: ":1.596", reply-serial: 120, body: Signature: [
s (115),
] }))
RHEL 8.7 returns value 1, with error:
Tag cannot be use in trunk mode without enable-native
The failure reason of 8.7 is correct.
Expected results:
Additional info:
On RHEL 9.1, though `nmstatectl apply` got value 65, using wrapped python API in CLI would get the error value 1, which is same with RHEL 8.
You desired yaml has two problems:
* Overlapping trunk tags.
* Tag cannot be use in trunk mode without enable-native
Patch posted to upstream: https://github.com/nmstate/nmstate/pull/2159
Add checks for these invalid use cases:
* VLAN trunk mode with tag defined but without `enable-native: true`.
* Overlap of VLAN trunk tags.
* Access mode with `enable-native: true` defined.
* Trunk mode without trunk-tags defined.
* Access mode with trunk-tags defined.
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: Some failure reasons and return values are different between rust and python version. Version-Release number of selected component (if applicable): nmstate-2.1.1-0.alpha.20220519.437e4a9.el9.x86_64 How reproducible: Steps to Reproduce: For example, when using "nmstatectl apply" such a state in command line: interfaces: - name: br0 type: linux-bridge state: up bridge: options: stp: enabled: true port: - name: veth0 vlan: mode: trunk tag: 200 trunk-tags: - id-range: min: 600 max: 900 - id: 800 - id-range: max: 500 min: 400 - name: veth1 vlan: mode: trunk tag: 200 trunk-tags: - id-range: min: 600 max: 900 - id: 800 - id-range: max: 500 min: 400 ipv4: enabled: true dhcp: true ipv6: enabled: true autoconf: true dhcp: true Actual results: RHEL 9.1 returns value 65, with error: NmstateError: Bug: DbusConnectionError: org.freedesktop.NetworkManager.Settings.Connection.InvalidProperty: bridge-port.vlans: duplicate bridge VLAN vid 800 dbus: Some(MethodError("org.freedesktop.NetworkManager.Settings.Connection.InvalidProperty", Some("bridge-port.vlans: duplicate bridge VLAN vid 800"), Msg { type: Error, sender: ":1.596", reply-serial: 120, body: Signature: [ s (115), ] })) RHEL 8.7 returns value 1, with error: Tag cannot be use in trunk mode without enable-native The failure reason of 8.7 is correct. Expected results: Additional info: On RHEL 9.1, though `nmstatectl apply` got value 65, using wrapped python API in CLI would get the error value 1, which is same with RHEL 8.