Bug 1740584

Summary: Ignore not active failure when deactivate
Product: Red Hat Enterprise Linux 8 Reporter: Gris Ge <fge>
Component: nmstateAssignee: Gris Ge <fge>
Status: CLOSED ERRATA QA Contact: Mingyu Shi <mshi>
Severity: high Docs Contact:
Priority: high    
Version: 8.1CC: jiji, jishi, network-qe
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: nmstate-0.0.8-9.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 20:52:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gris Ge 2019-08-13 10:10:40 UTC 
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
Comment 1 Gris Ge 2019-08-14 03:11:06 UTC 
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
```
Comment 6 errata-xmlrpc 2019-11-05 20:52:18 UTC 
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