Bug 1862702

Summary: Fail to add runtime bond to NetworkManager after rollback
Product: Red Hat Enterprise Linux 8 Reporter: Mingyu Shi <mshi>
Component: nmstateAssignee: Gris Ge <fge>
Status: CLOSED ERRATA QA Contact: Mingyu Shi <mshi>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.3CC: ferferna, jiji, jishi, network-qe, till
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nmstate-1.0.2-0.1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-05-18 15:17:12 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:
Bug Depends On: 1870691    
Bug Blocks:    
Attachments:
Description Flags
script.sh
none
log
none
verified.log none

Description Mingyu Shi 2020-08-01 14:35:43 UTC 
Created attachment 1703174 [details]
script.sh

Description of problem:
It's similar as #bz1861263 , but if there is a rollback in the middle, then it will fail when trying again.

Version-Release number of selected component (if applicable):
nmstate-0.3.4-7.el8.noarch
NetworkManager-1.26.0-2.el8.x86_64
DISTRO=RHEL-8.3.0-20200728.n.0
Linux hpe-dl380pgen8-02-vm-9.hpe2.lab.eng.bos.redhat.com 4.18.0-228.el8.x86_64 #1 SMP Mon Jul 27 06:05:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

How reproducible:
100%

Steps to Reproduce:
!!Make sure there is no interface 'no-eth1' and 'no-eth2' in the beginning
1. ./script.sh
2. ip link add no-eth1 type veth peer no-eth2
3. ./script.sh

Actual results:
Failed

Expected results:
No failure

Additional info:
Comment 1 Mingyu Shi 2020-08-01 14:40:07 UTC 
Created attachment 1703175 [details]
log

Run the commands(as in script.sh), it rollbacked as no-eth1 didn't exist, then I created no-eth1 and ran the commands again, but it failed.
Comment 2 Gris Ge 2020-08-20 15:31:35 UTC 
The simplified reproducer could be create a bond with iproute tool and ask nmstate to change the bond mode.


This is caused by a NetworkManager bug 1870691
Comment 4 Gris Ge 2021-02-05 09:00:26 UTC 
Hi Mingyu,


Can you do preverify against `dnf copr enable networkmanager/NetworkManager-master`?

Thank you!
Comment 5 Mingyu Shi 2021-02-10 09:08:55 UTC 
Gris, it works on:
nmstate-1.0.2-0.1.el8.noarch
nispor-1.0.1-3.el8.x86_64
NetworkManager-1.30.0-0.8.el8.x86_64

Run reproducer, no error.
Comment 8 Mingyu Shi 2021-02-15 06:44:32 UTC 
Created attachment 1757026 [details]
verified.log

Verified with versions:
nmstate-1.0.2-0.1.el8.noarch
nispor-1.0.1-3.el8.x86_64
NetworkManager-1.30.0-0.9.el8.x86_64
Comment 10 errata-xmlrpc 2021-05-18 15:17:12 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 (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:1748