Created attachment 1092634 [details] Screenshot for status page Description of problem: It shows "Networking: Unknown ovirtmgmt" in status page after register to rhevm3.6 succeed. Version-Release number of selected component (if applicable): rhev-hypervisor-7-7.2-20151104.0.e17ev ovirt-node-3.6.0-0.20.20151103git3d3779a.el7ev.noarch ovirt-node-plugin-vdsm-0.6.1-2.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. TUI clean install rhevh 2. Login rhevh, setup network via dhcp 3. Register to rhevm3.6 Actual results: 1. After step3, it shows "Networking: Unknown ovirtmgmt" in status page. Expected results: 1.After step3, it should show "Networking: Connected ovirtmgmt" in status page. Additional info:
Please attach the sosreport. We need to see if there are ifcfg files and the NIC has an IP.
Created attachment 1093062 [details] sosreport
Created attachment 1093063 [details] output of ifconfig
This is not nice, but a TUI only issue, thus lowering thej priority.
*** Bug 1282313 has been marked as a duplicate of this bug. ***
Also encounter this issue, but a bit different in rhev-hypervisor-7-7.2-20151210.1.e17ev. After rhevh register to rhevm successful, it shows "Networking: Unknown" in status page, and it shows "Unconfigured" for NIC in Network page. Test Steps: 1. TUI clean install rhevh 2. Login rhevh, setup network via dhcp 3. Register to rhevm3.6 Actual results: 1. After step3, it shows "Networking: Unknown" in status page, and it shows "Unconfigured" for NIC in Network page. Expected results: 1.After step3, it should show "Networking: Connected ovirtmgmt" in status page, and it shows "Managed" for NIC in Network page.
(In reply to Huijuan Zhao from comment #7) > Also encounter this issue, but a bit different in > rhev-hypervisor-7-7.2-20151210.1.e17ev. > > After rhevh register to rhevm successful, it shows "Networking: Unknown" in > status page, and it shows "Unconfigured" for NIC in Network page. > > Test Steps: > 1. TUI clean install rhevh > 2. Login rhevh, setup network via dhcp > 3. Register to rhevm3.6 > > Actual results: > 1. After step3, it shows "Networking: Unknown" in status page, and it shows > "Unconfigured" for NIC in Network page. > > Expected results: > 1.After step3, it should show "Networking: Connected ovirtmgmt" in status > page, and it shows "Managed" for NIC in Network page. Huijuan, see your comment, the issue is getting worse. I can imagine the impact is after RHEV-H register to RHEVM, then all related network TUI components, can not work well, example: RHN, Logging, Remote Storage, these TUI display "Networking is not configured". This reminds me of one bug 1088875(VERIFIED), see comment 5 of bug 1088875. Could you work with Chen to confirm whether new regression happen on RHEV-H 7.2 for beta 2 for bug 1088875?
Ying, I checked as comment 5 of bug 1088875, the workaround is effective: After register rhevm, enter into "RHEV-M" page of rhevh setup menu again, then it shows "Managed" for NIC in Network page, It shows "Networking: Unknown ovirtmgmt" in status page.
This might be related to bug 1289028
*** Bug 1291608 has been marked as a duplicate of this bug. ***
Please retest with latest release. There was general network/registration problem before If still happens please provide env.
(In reply to Anatoly Litovsky from comment #12) > Please retest with latest release. > There was general network/registration problem before > If still happens please provide env. This can be reproduced without too much work. MANAGED_IFACES is set to "" in /etc/default/ovirt (until the RHEV-M/Engine page is selected again after registration) ovirt.node.utils.network.BridgedNIC.is_configured needs to be smarter
Test version: rhev-hypervisor7-7.2-20160113.0 ovirt-node-3.6.1-3.0.el7ev.noarch Test steps: 1. TUI clean install rhevh 2. Login rhevh, setup network via dhcp 3. Register to rhevm3.6 4. Add RHEV-H from RHEV-M side. Test result: 1. Step 3 & 4, Networking show as: Connected ovirtmgmt" in status page. So the bug is fixed, change bug status to VERIFIED.
Note: for re-verification, please ensure that there's a VM running. With the original patch merged, it appears that the 2nd patch fails if there are VMs running, since vnetX may be selected instead (which has no configuration). This is the cause of the very similar HE bug.
(In reply to Ryan Barry from comment #17) > Note: for re-verification, please ensure that there's a VM running. > > With the original patch merged, it appears that the 2nd patch fails if there > are VMs running, since vnetX may be selected instead (which has no > configuration). This is the cause of the very similar HE bug. Thank you very much for your kind explanation :)
(In reply to Ryan Barry from comment #17) > Note: for re-verification, please ensure that there's a VM running. > > With the original patch merged, it appears that the 2nd patch fails if there > are VMs running, since vnetX may be selected instead (which has no > configuration). This is the cause of the very similar HE bug. Re-test with latest build: rhev-hypervisor7-7.2-20160222.0 ovirt-node-3.6.1-7.0.el7ev.noarch Test steps: 1. TUI clean install rhevh 2. Login rhevh, setup network via dhcp 3. Register to rhevm3.6 4. Add RHEV-H from RHEV-M side. 5. Create VM. 6. Run vm 7. Shutdown vm. Test result: 1. Step 1-4, Networking show as: Connected ovirtmgmt" in status page. 2. Step 5-6. Networking show as: unknown ovirtmgmt" in status page. 3. Step 7, Networking show as: Connected ovirtmgmt" in status page. Hi Ryan, Do we need re-open this bug? Thanks!
Created attachment 1130037 [details] vm-up-down
Created attachment 1130039 [details] re-verify-log
(In reply to shaochen from comment #19) > (In reply to Ryan Barry from comment #17) > > Note: for re-verification, please ensure that there's a VM running. > > > > With the original patch merged, it appears that the 2nd patch fails if there > > are VMs running, since vnetX may be selected instead (which has no > > configuration). This is the cause of the very similar HE bug. > > Re-test with latest build: > rhev-hypervisor7-7.2-20160222.0 > ovirt-node-3.6.1-7.0.el7ev.noarch > > Test steps: > 1. TUI clean install rhevh > 2. Login rhevh, setup network via dhcp > 3. Register to rhevm3.6 > 4. Add RHEV-H from RHEV-M side. > 5. Create VM. > 6. Run vm > 7. Shutdown vm. > > Test result: > 1. Step 1-4, Networking show as: Connected ovirtmgmt" in status page. > 2. Step 5-6. Networking show as: unknown ovirtmgmt" in status page. > 3. Step 7, Networking show as: Connected ovirtmgmt" in status page. > > Hi Ryan, > > Do we need re-open this bug? > > Thanks! The fix will be the same as the other bug (HE shows unknown ovirtmgmt). Re-opening would result in one of the two being closed as a duplicate, which is ok, but just FYI. I'll leave it to QE to decide
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0378.html