Bug 1362358

Summary: The slave NICs can not be up after delete master bond
Product: Red Hat Enterprise Linux 7 Reporter: Huijuan Zhao <huzhao>
Component: cockpitAssignee: Marius Vollmer <mvollmer>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0CC: bugs, cshao, dguo, fdeutsch, huzhao, jiawu, leiwang, rbarry, weiwang, yaniwang, ycui, yzhao
Target Milestone: pre-dev-freezeKeywords: Extras
Target Release: 7.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-10 13:02:19 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:    
Bug Blocks: 1304509    
Attachments:
Description Flags
kickstart file
none
screenshot of error report in cockpit
none
All logs
none
All ifcfg files in /etc/sysconfig/network-scripts none

Description Huijuan Zhao 2016-08-02 03:31:10 UTC
Created attachment 1186644 [details]
kickstart file

Description of problem:
Add bond1 on two NICs, after delete bond1, the two slave NICs can not be up or enable, there is error report:
Unexpected error
Master connection not found or invalid


Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.0-20160727.1.x86_64
imgbased-0.7.3-0.1.el7ev.noarch
cockpit-0.114-2.el7.x86_64
cockpit-ovirt-dashboard-0.10.6-1.3.3.el7ev.noarch
libvirt-daemon-driver-network-1.2.17-13.el7_2.5.x86_64
glib-networking-2.42.0-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install redhat-virtualization-host-4.0-20160727.1.x86_64 with kickstart file in attachment
2. Login RHVH via cockpit, change to Networking page
3. Add bond1 (Active-backup mode) on two NICs p3p1 and p4p1
4. Delete bond1
5. Enter p3p1 or p4p1, click "on"


Actual results:
1. After step5, enable p3p1 and p4p1 failed, there is error report:
Unexpected error
Master connection not found or invalid

Expected results:
1. After step5, should enable p3p1 and p4p1 successful without error.


Additional info:

Comment 1 Huijuan Zhao 2016-08-02 03:31:55 UTC
Created attachment 1186645 [details]
screenshot of error report in cockpit

Comment 2 Huijuan Zhao 2016-08-02 03:33:02 UTC
Created attachment 1186646 [details]
All logs

Comment 3 Huijuan Zhao 2016-08-02 03:33:58 UTC
Created attachment 1186647 [details]
All ifcfg files in /etc/sysconfig/network-scripts

Comment 4 Fabian Deutsch 2016-08-03 10:50:31 UTC
This sounds like a Cockpit bug.

Comment 5 Fabian Deutsch 2016-08-25 07:31:35 UTC
This bug is not really blocked by bug 1304509 - but it is related.

Comment 7 Dominik Perpeet 2016-09-06 19:18:25 UTC
What state are the two NICs in before a bond is added? I can't reproduce the issue here.
Does the process work if you run all the steps via nmcli?

Comment 8 Huijuan Zhao 2016-09-08 03:29:48 UTC
(In reply to Dominik Perpeet from comment #7)
> What state are the two NICs in before a bond is added? I can't reproduce the
> issue here.

The two NICs are up before a bond is added

> Does the process work if you run all the steps via nmcli?

If I write ifcfg file via nmcli same as cockpit produced, also encounter this issue. 
But after I remove "MASTER=XXXXXX" from ifcfg-p3p1, "ifup p3p1" works well, so I guess the issue maybe the "MASTER=XXXXXX" in NICs ifcfg file.

Comment 9 Marius Vollmer 2016-11-10 13:02:19 UTC

*** This bug has been marked as a duplicate of bug 1355656 ***