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

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.

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

Hi Mingyu,


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

Thank you!

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.

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

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