Bug 1367320 - Cockpit does not show unmanaged devices
Summary: Cockpit does not show unmanaged devices
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit
Version: 7.2
Hardware: All
OS: Linux
Target Milestone: pre-dev-freeze
: 7.4
Assignee: Marius Vollmer
QA Contact: qe-baseos-daemons
Depends On:
Blocks: ovirt-node-ng-platform
TreeView+ depends on / blocked
Reported: 2016-08-16 08:17 UTC by Yihui Zhao
Modified: 2017-10-13 10:20 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-10-13 10:20:27 UTC
Target Upstream Version:

Attachments (Terms of Use)
The NIC information on cockpit. (112.99 KB, image/png)
2016-08-16 08:17 UTC, Yihui Zhao
no flags Details
The NIC information in "/etc/sysconfig/network-scripts" (95.75 KB, image/png)
2016-08-16 08:18 UTC, Yihui Zhao
no flags Details
The log about sosreport and /var/log. (6.23 MB, application/x-gzip)
2016-08-16 08:22 UTC, Yihui Zhao
no flags Details
10 interfaces in Cockpit (137.03 KB, image/png)
2016-08-17 10:35 UTC, Marius Vollmer
no flags Details

Description Yihui Zhao 2016-08-16 08:17:44 UTC
Created attachment 1191136 [details]
The NIC information on cockpit.

Description of problem:
The NIC information display incompletely on Cockpit when the number of nic larger than six.
And the NIC which has its ip don't display on cockpit.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install RHVH rhvh-4.0-0.20160812.0
2. Login cockpit via "ip:9090"
3. Enter to Networking page

Actual results:
The NIC which has its ip don't display on cockpit.

Expected results:
All of the NIC information should be display on cockpit.
Additional info:
The number of NIC should be larger than six can reproduce the bug.

Comment 1 Red Hat Bugzilla Rules Engine 2016-08-16 08:17:52 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 Yihui Zhao 2016-08-16 08:18:39 UTC
Created attachment 1191137 [details]
The NIC information in "/etc/sysconfig/network-scripts"

Comment 3 Yihui Zhao 2016-08-16 08:22:30 UTC
Created attachment 1191140 [details]
The log about sosreport and /var/log.

Comment 5 Marius Vollmer 2016-08-17 10:22:44 UTC
Please also attach the output of "nmcli con" and "nmcli dev".

Comment 6 Marius Vollmer 2016-08-17 10:34:38 UTC
I could add 10 network interfaces on a virtual machine without trouble, see the attached screenshot.

In you screenshot, em2 seems to be missing.  It is probably omitted for some specific reason or bug.  There is no limit to 6 interfaces anywhere that I know of.

Please try to figure out why em2 is not shown.  "nmcli dev" might give some hints.
Please also try "nmtui" to see whether it shows different interfaces than Cockpit.

Comment 7 Marius Vollmer 2016-08-17 10:35:23 UTC
Created attachment 1191565 [details]
10 interfaces in Cockpit

Comment 8 Yihui Zhao 2016-08-17 12:30:06 UTC
(In reply to Marius Vollmer from comment #5)
> Please also attach the output of "nmcli con" and "nmcli dev".

Hi Marius,
The output of "nmcli con" and "nmcli dev" list here:

[root@bootp-73-75-188 ~]# nmcli con                                             
NAME  UUID                                  TYPE            DEVICE              
p1p1  251b14ce-1577-4ef8-aeba-cf122ab14cca  802-3-ethernet  --                  
p2p2  0145f623-9114-4c48-b783-7cc313dd7298  802-3-ethernet  --                  
p3p2  7158af56-4921-447f-bce8-c79b5cd7e269  802-3-ethernet  --                  
p3p1  2f983e74-183f-4351-9c95-9b18c942a346  802-3-ethernet  --                  
em1   f194dc02-7d2f-47cd-ba42-dd559afc9848  802-3-ethernet  --                  
p2p1  11c0f9a2-70e7-48ec-9af4-8ee77945f68a  802-3-ethernet  --    

   [root@bootp-73-75-188 ~]# nmcli dev                                             
DEVICE  TYPE      STATE         CONNECTION                                      
em1     ethernet  disconnected  --                                              
p1p1    ethernet  disconnected  --                                              
p2p1    ethernet  disconnected  --                                              
p2p2    ethernet  disconnected  --                                              
p3p1    ethernet  disconnected  --                                              
p3p2    ethernet  disconnected  --                                              
em2     ethernet  unmanaged     --                                              
lo      loopback  unmanaged     --  

My testing environment is activate one nic about em2.

Comment 9 Marius Vollmer 2016-09-09 09:31:43 UTC
> em2     ethernet  unmanaged     --

This is the reason why Cockpit doesn't show the em2 interface.  It doesn't show any unmanaged interfaces.

I think we can argue that Cockpit _should_ in fact show unmanaged interfaces, but refrain from configuring them.  I'll propose that via a pull request.

Comment 10 Fabian Deutsch 2016-09-10 10:18:35 UTC
+1 on that suggested behavior Marius.

Comment 11 Marius Vollmer 2016-09-15 08:42:43 UTC
Here is the pull request:


With that, your em2 should appear in its own "Unmanaged Interfaces" panel.

Whether or not "em2" should actually be unmanaged is a different question.  Do you think it might be erroneously marked as unmanaged by NM?

Comment 12 Dominik Perpeet 2016-12-13 22:11:00 UTC
The patch went into upstream Cockpit 119, available in 7.3.1 with version cockpit-122

Comment 13 Martin Pitt 2017-10-13 10:20:27 UTC
This was fixed upstream in Cockpit 127, current RHEL 7.4 has Cockpit 138, so this bug is fixed there. Plus this was fixed as an update in 7.3.1. So I think this can be closed now.

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