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.
Created attachment 1667645[details]
failure logs
Description of problem:
Got failure when veth and dummy both are in team.ports
Version-Release number of selected component (if applicable):
nmstate-0.2.6-1.el8.noarch
NetworkManager-1.22.8-1.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
# cat team0.yaml
---
interfaces:
- name: team0
state: up
type: team
team:
ports:
- name: vethteam0
- name: dummy0
1. ip link add vethteam0 type veth peer name vethteam0_ep
nmcli dev set vethteam0 managed yes
2. nmstatectl set team0.yaml
3.
Actual results:
Got failure
Expected results:
No failure
Additional info:
It's ok to create as all-dummy or all-veth, but put them together.
Update: it is due to the order of the slave names, nothing to do with veth and slave
ports:
- name: a
- name: b
will be ok, but
ports:
- name: b
- name: a
will get a failure
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-2020:4696
Created attachment 1667645 [details] failure logs Description of problem: Got failure when veth and dummy both are in team.ports Version-Release number of selected component (if applicable): nmstate-0.2.6-1.el8.noarch NetworkManager-1.22.8-1.el8.x86_64 How reproducible: 100% Steps to Reproduce: # cat team0.yaml --- interfaces: - name: team0 state: up type: team team: ports: - name: vethteam0 - name: dummy0 1. ip link add vethteam0 type veth peer name vethteam0_ep nmcli dev set vethteam0 managed yes 2. nmstatectl set team0.yaml 3. Actual results: Got failure Expected results: No failure Additional info: It's ok to create as all-dummy or all-veth, but put them together.