Bug 1401418 - Cockpit can not handle interfaces which are setup by manual configure ifcfg files
Summary: Cockpit can not handle interfaces which are setup by manual configure ifcfg f...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit
Version: 7.3
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: pre-dev-freeze
: ---
Assignee: Marius Vollmer
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1400961
TreeView+ depends on / blocked
 
Reported: 2016-12-05 08:06 UTC by Huijuan Zhao
Modified: 2017-01-02 12:32 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-02 12:32:03 UTC
Target Upstream Version:


Attachments (Terms of Use)
All logs and all files in /etc/sysconfig/network-scripts/ (8.33 MB, application/x-gzip)
2016-12-05 08:06 UTC, Huijuan Zhao
no flags Details
Screenshot of unmanaged Interfaces in cockpit (128.14 KB, image/png)
2016-12-05 08:07 UTC, Huijuan Zhao
no flags Details

Description Huijuan Zhao 2016-12-05 08:06:16 UTC
Created attachment 1228003 [details]
All logs and all files in /etc/sysconfig/network-scripts/

Description of problem:
Setup ifcfg files manually for NIC, it shows "Unmanaged Interfaces" in Cockpit


Version-Release number of selected component (if applicable):
redhat-virtualization-host-4.0-20161130.0
imgbased-0.8.10-0.1.el7ev.noarch
cockpit-ws-122-3.el7.x86_64
NetworkManager-1.4.0-13.el7_3.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install RHVH via interactive anaconda.
2. Reboot RHVH and login, setup /etc/sysconfig/network-scripts/ifcfg-interfacename files for two NICs p3p1 and p4p1(create bond1.20 over p3p1 and p4p1) (please refer to attachment for detailed configure)
3. Reboot RHVH and login Cockpit, enter Networking page, focus on interface status

Actual results:
After step3, it shows the two NICs p3p1 and p4p1 are "Unmanaged Interfaces", can not configure them via cockpit

Expected results:
After step4, cockpit should can handle all interfaces

Additional info:

Comment 1 Huijuan Zhao 2016-12-05 08:07:11 UTC
Created attachment 1228004 [details]
Screenshot of unmanaged Interfaces in cockpit

Comment 3 Marius Vollmer 2017-01-02 12:32:03 UTC
The ifcfg files contain NM_CONTROLLED=no, which explicitly puts them into the "Unmanaged Interfaces" section.

Removing NM_CONTROLLED=no should make them manageable via Cockpit.


Note You need to log in before you can comment on or make changes to this bug.