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:

Got failure when creating team interface via nmstatectl.

2020-02-06 17:54:00,729 root         ERROR    NM main-loop aborted: Connection activation failed on team0: reason=<enum NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED of type NM.ActiveConnectionStateReason>


Version-Release number of selected component (if applicable):
NetworkManager-team-1.22.6-1.el8.x86_64
teamd-1.29-1.el8.x86_64
libteam-1.29-1.el8.x86_64
nmstate-0.2.3-1.el8.noarch

How reproducible:
1%

Steps to Reproduce:

for x in `seq 1 100`; do
    sudo ncl set team0_up.yml && \
    sudo ncl set team0_absent.yml && \
    sleep 1 || \
    break;
    echo $x;
done;
echo $x;

Actual results:
Got failure of NM_ACTIVE_CONNECTION_STATE_REASON_DEVICE_DISCONNECTED

Expected results:
No failure

Additional info:
At the time this failure happens, I used:

nm_dev = NM.Client.get_device_by_iface(devname)
new_ac = nm_dev.get_active_connection()

The new_ac is identical to current NM.ActiveConnection.

Created attachment 1658144 [details]
team0_up.yml

Created attachment 1658155 [details]
team0_absent.yml

Created attachment 1658156 [details]
System logs with NM trace enabled

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/410

Fixed upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/a119dac99815f4736cb9b3b11a7732bc4c8b32b0

covered by the nmstate test executing nmstate's CI.

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:1847