Created attachment 1167758 [details] network page Description of problem: It miss to show the network status after register to RHEVM. And it should remove ";vdsmdummy;" in cockpit after register to RHEVM also. Version-Release number of selected component (if applicable): rhev-hypervisor7-ng-4.0-20160608.0.x86_64 cockpit-ovirt-dashboard-0.10.3-0.0.1.el7ev.noarch imgbased-0.7.0-0.1.el7ev.noarch redhat-release-rhev-hypervisor-4.0-0.6.el7.x86_64 vdsm-4.18.2-0.el7ev.x86_64 How reproducible: 100% Whiteboard: UI Not regression bug Steps to Reproduce: 1. install rhev-hypervisor7-ng-4.0-20160608.0.x86_64 2. Register to RHEVM 3. Check the network page in cockpit Actual results: 1. It miss to show the network status after register to RHEVM. 2. It shows ";vdsmdummy;" as a interface. Expected results: 1. It should show the network status after register to RHEVM. 2. It should remove ";vdsmdummy;" as a interface Additional info:
Please do not mix two issues in one bug, thus create a separate bug for the ";vdsmdummy;" interface. It can actually well be, that the network status in cockpit after registration to RHEV-M is limited, because after registration the NIC management is done by vdsm, and not NM anymore. According to the screenshot it looks like the IP address and other informations are not shown, so before closing this bug it would be interestingto know if we could show those informations using NM, even if the NIC is not managed by NM.
(In reply to Fabian Deutsch from comment #1) > Please do not mix two issues in one bug, thus create a separate bug for the > ";vdsmdummy;" interface. Report a new bug to track this issue. https://bugzilla.redhat.com/show_bug.cgi?id=1348388 > > It can actually well be, that the network status in cockpit after > registration to RHEV-M is limited, because after registration the NIC > management is done by vdsm, and not NM anymore. > > According to the screenshot it looks like the IP address and other > informations are not shown, so before closing this bug it would be > interestingto know if we could show those informations using NM, even if the > NIC is not managed by NM.
*** Bug 1362006 has been marked as a duplicate of this bug. ***
Test Version 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 Steps: 1. Install redhat-virtualization-host-4.0-20160727.1.x86_64 with kickstart file in attachment 2. Add host to RHVM 3. Login cockpit website hostIP:9090 with root account 4. Select "Networking" page 5. Check the interface information Result: 1. Physical network interface using for RHEVM and ovirtmgmt is still missed in cockpit networking page. 2. ";vdsmdummy;" is removed as an interface
Created attachment 1186302 [details] ks file
Created attachment 1186314 [details] picture
Closing this bug until the final networking situation for Node is clear.
Still encounter this issue in the build redhat-virtualization-host-4.0-20161130.0, re-open it.
The actual result is different with Comment 0 in redhat-virtualization-host-4.0-20161206.0. Steps to Reproduce: 1. Install redhat-virtualization-host-4.0-20161206.0 2. Reboot and login RHVH, set up NIC em1 IP via cockpit 3. Add RHVH to RHVM 4. Check the Networking page in cockpit Actual results: In step4, ";vdsmdummy;", "em1" and "ovirtmgmt" are all in "Unmanaged Interfaces", please refer to attachment(screenshot of network show) for detailed info.
Created attachment 1229394 [details] screenshot of network show
I think this is correct, because the interfaces are managed by vdsm (thus unmanaged by cockpit/NM) and not by cockpit/NM anymore. Interfaces which are managed by NM are then called managed. Considering this, then comment 10 is not a bug, but rather the expected behavior.
Update: (In reply to Huijuan Zhao from comment #10) > The actual result is different with Comment 0 in > redhat-virtualization-host-4.0-20161206.0. > > Steps to Reproduce: > 1. Install redhat-virtualization-host-4.0-20161206.0 > 2. Reboot and login RHVH, set up NIC em1 IP via cockpit > 3. Add RHVH to RHVM > 4. Check the Networking page in cockpit 5. Reboot RHVH, check the Networking page in cockpit again > > Actual results: > In step4, ";vdsmdummy;", "em1" and "ovirtmgmt" are all in "Unmanaged > Interfaces", > please refer to attachment(screenshot of network show) for detailed info. In step5, It miss to show the network status. There is nothing in Networking page in cockpit, same as comment 0. Expected results: In step5, should show same as step4. So I think this bug is not resolved completely, I will reopen this bug.
Can you please post the contents of /etc/sysconfig/network-scripts/ifcfg-${if} ? I would expect this to be the case if VDSM turns off NM management. Cockpit only knows how to pull interface information from NetworkManager, not any other system processes. If NetworkManager is disabled (or the interfaces have NM_CONTROLLED=no), cockpit will not show any information for them. This is expected behavior.
Created attachment 1232454 [details] comment 13&14: ifcfg-${if} files
Created attachment 1232455 [details] comment 13&14: screenshot of Networking in cockpit
(In reply to Ryan Barry from comment #14) > Can you please post the contents of > /etc/sysconfig/network-scripts/ifcfg-${if} ? > Please refer to attachment " comment 13&14: ifcfg-${if} files". Additional info: # service NetworkManager status Redirecting to /bin/systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: man:NetworkManager(8) # ip a s 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovirtmgmt state UP qlen 1000 link/ether 08:94:ef:21:c0:4d brd ff:ff:ff:ff:ff:ff 3: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 08:94:ef:21:c0:4e brd ff:ff:ff:ff:ff:ff 4: eno3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 08:94:ef:21:c0:4f brd ff:ff:ff:ff:ff:ff 5: eno4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 08:94:ef:21:c0:50 brd ff:ff:ff:ff:ff:ff 6: ens5f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 00:1b:21:6e:07:4c brd ff:ff:ff:ff:ff:ff 7: ens5f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 00:1b:21:6e:07:4d brd ff:ff:ff:ff:ff:ff 8: enp0s20u1u5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 0a:94:ef:21:c0:54 brd ff:ff:ff:ff:ff:ff 9: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000 link/ether 08:94:ef:21:c0:4d brd ff:ff:ff:ff:ff:ff inet 10.73.130.225/23 brd 10.73.131.255 scope global dynamic ovirtmgmt valid_lft 42702sec preferred_lft 42702sec 10: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether b2:c3:9c:6e:c5:16 brd ff:ff:ff:ff:ff:ff
Created attachment 1322557 [details] After add host to RHEVM
Try to test this issue on rhvh-4.1-0.20170831.0+1 build Test Version Version-Release number of selected component (if applicable): redhat-virtualization-host-4.1-20160831.1.x86_64 imgbased-0.9.47-0.1.el7ev.noarch cockpit-ws-141-4.el7.x86_64 cockpit-ovirt-dashboard-0.10.7-0.0.23.el7ev.noarch Test steps: 1. Install redhat-virtualization-host-4.1-20160831.1.x86_64 via iso 2. Add host to RHEVM 3. Login cockpit website hostIP:9090 with root account 4. Select "Networking" page 5. Check the interface information 6. Check host network info 7. Reboot system and check the interface information again Test results: 1.After step 5, ";vdsmdummy;", "em1" and "ovirtmgmt" are all in "Unmanaged Interfaces" 2.After step 6, #ip a s(diff between before add host to RHEVM and after add host to RHEVM) 7c7 < 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 --- > 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovirtmgmt state UP qlen 1000 9,14d8 < inet 10.73.194.126/23 brd 10.73.195.255 scope global dynamic eno1 < valid_lft 42781sec preferred_lft 42781sec < inet6 2620:52:0:49c2:1277:f71:dac2:98b8/64 scope global noprefixroute dynamic < valid_lft 2591858sec preferred_lft 604658sec < inet6 fe80::b764:1da4:7597:47e2/64 scope link < valid_lft forever preferred_lft forever 24a19,28 > 23: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 > link/ether ae:1b:f6:a9:ed:e9 brd ff:ff:ff:ff:ff:ff > 24: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000 > link/ether 28:80:23:ae:2a:88 brd ff:ff:ff:ff:ff:ff > inet 10.73.194.126/23 brd 10.73.195.255 scope global dynamic ovirtmgmt > valid_lft 43131sec preferred_lft 43131sec > inet6 2620:52:0:49c2:2a80:23ff:feae:2a88/64 scope global mngtmpaddr dynamic > valid_lft 2591977sec preferred_lft 604777sec > inet6 fe80::2a80:23ff:feae:2a88/64 scope link > valid_lft forever preferred_lft forever 3.After step 7, still ";vdsmdummy;", "em1" and "ovirtmgmt" are all in "Unmanaged Interfaces" Expected results: 1. It should show the network status after register to RHEVM. 2. It should remove ";vdsmdummy;" as a interface 3. Detail info, please come to attachment 1322557 [details] about the cockpit screenshot According to the above message, I think this bug is not resolved correctly
(In reply to jianwu from comment #19) > Try to test this issue on rhvh-4.1-0.20170831.0+1 build > > Test Version > Version-Release number of selected component (if applicable): > redhat-virtualization-host-4.1-20160831.1.x86_64 > imgbased-0.9.47-0.1.el7ev.noarch > cockpit-ws-141-4.el7.x86_64 > cockpit-ovirt-dashboard-0.10.7-0.0.23.el7ev.noarch > > Test steps: > 1. Install redhat-virtualization-host-4.1-20160831.1.x86_64 via iso > 2. Add host to RHEVM > 3. Login cockpit website hostIP:9090 with root account > 4. Select "Networking" page > 5. Check the interface information > 6. Check host network info > 7. Reboot system and check the interface information again > > Test results: > 1.After step 5, ";vdsmdummy;", "em1" and "ovirtmgmt" are all in "Unmanaged > Interfaces" > > 2.After step 6, > #ip a s(diff between before add host to RHEVM and after add host to RHEVM) > 7c7 > < 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen > 1000 > --- > > 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovirtmgmt state UP qlen 1000 > 9,14d8 > < inet 10.73.194.126/23 brd 10.73.195.255 scope global dynamic eno1 > < valid_lft 42781sec preferred_lft 42781sec > < inet6 2620:52:0:49c2:1277:f71:dac2:98b8/64 scope global noprefixroute > dynamic > < valid_lft 2591858sec preferred_lft 604658sec > < inet6 fe80::b764:1da4:7597:47e2/64 scope link > < valid_lft forever preferred_lft forever > 24a19,28 > > 23: ;vdsmdummy;: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 > > link/ether ae:1b:f6:a9:ed:e9 brd ff:ff:ff:ff:ff:ff > > 24: ovirtmgmt: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000 > > link/ether 28:80:23:ae:2a:88 brd ff:ff:ff:ff:ff:ff > > inet 10.73.194.126/23 brd 10.73.195.255 scope global dynamic ovirtmgmt > > valid_lft 43131sec preferred_lft 43131sec > > inet6 2620:52:0:49c2:2a80:23ff:feae:2a88/64 scope global mngtmpaddr dynamic > > valid_lft 2591977sec preferred_lft 604777sec > > inet6 fe80::2a80:23ff:feae:2a88/64 scope link > > valid_lft forever preferred_lft forever > > 3.After step 7, still ";vdsmdummy;", "em1" and "ovirtmgmt" are all in > "Unmanaged Interfaces" > > Expected results: > 1. It should show the network status after register to RHEVM. > 2. It should remove ";vdsmdummy;" as a interface > 3. Detail info, please come to attachment 1322557 [details] about the > cockpit screenshot > > According to the above message, I think this bug is not resolved correctly Test on rhvh-4.1-0.20170925.0+1, this issue still exits
Dan, are we moving to NM in 4.2?
No. Network interfaces configured by Vdsm have NM_CONTROLLED=no.
Ryan, what's current status?
There aren't any current changes here. If engine/vdsm is configured to use NetworkManager, this works as expected. Maybe we can push for this as a default. If it's using the 'network' service, it will not. Cockpit accesses network information over NetworkManager's dbus interface, and will never support status from vintage network configuration.
re-targeting to 4.3.1 since this BZ has not been proposed as blocker for 4.3.0. If you think this bug should block 4.3.0 please re-target and set blocker flag.
Moving to 4.3.2 not being identified as blocker for 4.3.1
Dan, any plans on moving to NM-controlled network any time soon (ovirt 4.3 or 4.4)? If not, I would close this BZ on our side as CANTFIX. Thanks! Martin
We have real active plans to move to NM tracked by bug 1107803
Now that we moved to NetworkManager / nmstate, is this still reproducible on 4.4/el8 ?
Can this bug be closed?
(In reply to peyu from comment #32) > Can this bug be closed? Test steps: 1. Install redhat-virtualization-host-4.4.0-20200318.0.el8_2 (equivalent to oVirt Node beta but based on RHEL 8.2) and reboot 2. Add RHVH to RHVM (via NIC eno1) 3. Check the Networking page in cockpit Test results: 1) "ovirtmgmt" is in "Interfaces" 2) ";vdsmdummy;" is in "Unmanaged Interfaces" So yes, closing this with resolution next release.