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 1724163 - The slave NICs are still inactive after deleting bond successfully in cockpit.
Summary: The slave NICs are still inactive after deleting bond successfully in cockpit.
Keywords:
Status: CLOSED DUPLICATE of bug 1729378
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 7.8
Assignee: Marius Vollmer
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1724042
TreeView+ depends on / blocked
 
Reported: 2019-06-26 11:27 UTC by Sandro Bonazzola
Modified: 2019-10-22 06:22 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1724042
Environment:
Last Closed: 2019-08-01 13:29:10 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Sandro Bonazzola 2019-06-26 11:27:19 UTC 
+++ This bug was initially created as a clone of Bug #1724042 +++

Description of problem:
After deleting bond in cockpit, the slave NICs are still inactive status. According to test case, they should be up and get the DHCP IP.

Version-Release number of selected component (if applicable):
RHVH-4.3-20190620.7-RHVH-x86_64-dvd1.iso
cockpit-system-195-1.el7.noarch
cockpit-195-1.el7.x86_64
cockpit-bridge-195-1.el7.x86_64
cockpit-ws-195-1.el7.x86_64
cockpit-machines-ovirt-195-1.el7.noarch
cockpit-dashboard-195-1.el7.x86_64
cockpit-storaged-195-1.el7.noarch
cockpit-ovirt-dashboard-0.13.2-2.el7ev.noarch
NetworkManager-1.18.0-4.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Clean install RHVH-4.3-20190620.7-RHVH-x86_64-dvd1.iso
2. Login to  "http://localhost:9090"
3. Create bond with two dhcp NICs in Cockpit Network
4. Delete the bond
5. Check the slave NICs

Actual results:
The slave NICs are still inactive status after deleting bond successfully in cockpit.

Expected results:
The slave NICs should be up status and get the DHCP IP successfully.

Additional info:
Comment 2 Martin Pitt 2019-06-27 10:39:30 UTC 
@Marius, this is possibly a NetworkManager issue. Can you please have a look, and reassign if appropriate? Thanks!
Comment 3 Martin Pitt 2019-07-18 14:50:27 UTC 
The deadline for 7.7 changes has passed weeks before this was even reported, and this isn't really a regression. Unblocking for 7.7.
Comment 6 Marius Vollmer 2019-07-22 12:38:55 UTC 
(In reply to Sandro Bonazzola from comment #0)

> After deleting bond in cockpit, the slave NICs are still inactive status.
> According to test case, they should be up and get the DHCP IP.

What test case?
Comment 7 Wei Wang 2019-07-24 01:33:53 UTC 
(In reply to Marius Vollmer from comment #6)
> (In reply to Sandro Bonazzola from comment #0)
> 
> > After deleting bond in cockpit, the slave NICs are still inactive status.
> > According to test case, they should be up and get the DHCP IP.
> 
> What test case?

Cockpit network test case "Delete bridge through cockpit" (https://polarion.engineering.redhat.com/polarion/#/project/RHEVM3/workitem?id=RHEVM-23974)
Comment 8 Marius Vollmer 2019-07-24 12:19:15 UTC 
(In reply to Wei Wang from comment #7)
> (In reply to Marius Vollmer from comment #6)
> > (In reply to Sandro Bonazzola from comment #0)
> > 
> > > After deleting bond in cockpit, the slave NICs are still inactive status.
> > > According to test case, they should be up and get the DHCP IP.
> > 
> > What test case?
> 
> Cockpit network test case "Delete bridge through cockpit"
> (https://polarion.engineering.redhat.com/polarion/#/project/RHEVM3/
> workitem?id=RHEVM-23974)

Thanks, but I can't access that.

Please consider contributing automated test cases upstream: https://github.com/cockpit-project/cockpit
Then we can find regressions much earlier.
Comment 9 Marius Vollmer 2019-07-24 12:21:49 UTC 
I didn't investigate whether this is a regression, but I found that our current method of removing a slave from a bond is not enough to have NM actually act on it.  This should fix it: https://github.com/cockpit-project/cockpit/pull/12400
Comment 10 Martin Pitt 2019-08-01 13:29:10 UTC 
Bug 1729378 is almost the same and fixed in the same PR. Making this a duplicate, to avoid having to collect all acks twice.

*** This bug has been marked as a duplicate of bug 1729378 ***
Note You need to log in before you can comment on or make changes to this bug.