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:

The CI test case `test_add_bond_with_slaves_and_ipv4` will fail randomly
due to error:

        Connection deactivation failed on eth2: error=nm-manager-error-quark: The
        connection was not active.

Version-Release number of selected component (if applicable):
nmstate-0.0.8-6.el8

How reproducible:
10%

Steps to Reproduce:
1. Run upstream CI test `test_add_bond_with_slaves_and_ipv4`.
2.
3.

Actual results:

Fail(might need 10+ retry) with error:

Connection deactivation failed on eth2: error=nm-manager-error-quark: The
connection was not active.


Expected results:
No failure.

Additional info:

Upstream fix is a0439681e9dee5b3b5a2ff7cceebbe9b1a411cf0

Reproduce script:

for x in `seq 1 100`; do 
    (sudo nmstatectl set bond.yml && sudo nmstatectl set bond_absent.yml) || break; 
    echo $x; 
done



bond.yml:


```yml
---
interfaces:
- name: eth1
  state: up
- name: bond99
  type: bond
  state: up
  link-aggregation:
    mode: balance-rr
    slaves:
    - eth1
```


bond_absent.yml:

```yml
---
interfaces:
- name: bond99
  type: bond
  state: absent
```

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-2019:3347