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):
Steps to Reproduce:
1. Install RHVH rhvh-4.0-0.20160812.0
2. Login cockpit via "ip:9090"
3. Enter to Networking page
The NIC which has its ip don't display on cockpit.
All of the NIC information should be display on cockpit.
The number of NIC should be larger than six can reproduce the bug.
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.
Created attachment 1191137 [details]
The NIC information in "/etc/sysconfig/network-scripts"
Created attachment 1191140 [details]
The log about sosreport and /var/log.
Please also attach the output of "nmcli con" and "nmcli dev".
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.
Created attachment 1191565 [details]
10 interfaces in Cockpit
(In reply to Marius Vollmer from comment #5)
> Please also attach the output of "nmcli con" and "nmcli dev".
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.
> 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.
+1 on that suggested behavior Marius.
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?
The patch went into upstream Cockpit 119, available in 7.3.1 with version cockpit-122
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.