Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1749632

Summary: Detach slave will cause slave been removed.
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: blc, jiji, jishi, network-qe, sukulkar
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: nmstate-0.0.8-15.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 20:52:21 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:
Attachments:
Description Flags
br0_over_bond.yml
none
br0_over_bond_remove.yml
none
br0_over_bond.yml
none
br0_over_bond_remove.yml
none
reproducer.log none

Description Gris Ge 2019-09-06 05:02:15 UTC
Description of problem:

When detaching slave from bridge, the slave profile will be removed.

When the slave is software interface(like bond, vlan, etc), the interface
also got removed.

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

How reproducible:
100%

Steps to Reproduce:
1. sudo nmstatectl set br0_over_bond.yml
2. sudo nmstatectl set br0_over_bond_remove.yml
3. ip link show bond99

Actual results:

The bond99 got removed.

Expected results:

The bond99 is preserved.

Additional info:
Upstream fix is  https://github.com/nmstate/nmstate/pull/480

Comment 2 Gris Ge 2019-09-06 05:03:03 UTC
Created attachment 1612177 [details]
br0_over_bond.yml

Comment 3 Gris Ge 2019-09-06 05:03:25 UTC
Created attachment 1612178 [details]
br0_over_bond_remove.yml

Comment 7 Gris Ge 2019-09-19 13:42:21 UTC
Created attachment 1616743 [details]
br0_over_bond.yml

Comment 8 Gris Ge 2019-09-19 13:42:46 UTC
Created attachment 1616744 [details]
br0_over_bond_remove.yml

Comment 9 Gris Ge 2019-09-19 13:44:29 UTC
New reproduce files uploaded.

With nmstate-0.0.8-14.el8 or earlier version, it will fail with `libnmstate.error.NmstateVerificationError` exception complaining bond88 is marked as `down`.

With nmstate-0.0.8-15.el8, no error and bond88 still exists after `nmstatecctl set`.

Comment 10 Mingyu Shi 2019-09-20 05:52:15 UTC
Created attachment 1617030 [details]
reproducer.log

Comment 13 errata-xmlrpc 2019-11-05 20:52:21 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