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:
Now when configuring subordinate ports of a main interface, linux-bridge, bond, ovs-bridge, ovs-bond, vrf are using 'port', but team use 'ports' as the property name. We'd better to unify them. For the backward compatibility, nmstate should allow the old name, but reports only one name.
Version-Release number of selected component (if applicable):
nmstate-0.4.1-1.el8.noarch
How reproducible:
100%
Steps to Reproduce:
1. Configure a team interface
2. nmstatectl show
3. Check the team's property
Actual results:
interfaces:
- name: team0-0
type: team
state: up
ipv4:
enabled: false
address: []
dhcp: false
ipv6:
enabled: false
address: []
autoconf: false
dhcp: false
lldp:
enabled: false
mac-address: 9A:AE:EE:42:13:D5
mtu: 1500
team:
ports: # the other types of main interface are using 'port'
- name: dummy0-14
- name: dummy0-15
runner:
name: roundrobin
Expected results:
Show text 'port' instead of 'ports'
Additional info:
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-2021:4157
Description of problem: Now when configuring subordinate ports of a main interface, linux-bridge, bond, ovs-bridge, ovs-bond, vrf are using 'port', but team use 'ports' as the property name. We'd better to unify them. For the backward compatibility, nmstate should allow the old name, but reports only one name. Version-Release number of selected component (if applicable): nmstate-0.4.1-1.el8.noarch How reproducible: 100% Steps to Reproduce: 1. Configure a team interface 2. nmstatectl show 3. Check the team's property Actual results: interfaces: - name: team0-0 type: team state: up ipv4: enabled: false address: [] dhcp: false ipv6: enabled: false address: [] autoconf: false dhcp: false lldp: enabled: false mac-address: 9A:AE:EE:42:13:D5 mtu: 1500 team: ports: # the other types of main interface are using 'port' - name: dummy0-14 - name: dummy0-15 runner: name: roundrobin Expected results: Show text 'port' instead of 'ports' Additional info: