Bug 1300188 - Network status shows "Unknown ovirtmgmt" after register to rhevm3.6 with HE configured
Summary: Network status shows "Unknown ovirtmgmt" after register to rhevm3.6 with HE c...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-node
Version: 3.6.3
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Ryan Barry
QA Contact: cshao
URL:
Whiteboard:
Depends On:
Blocks: 1322783
TreeView+ depends on / blocked
 
Reported: 2016-01-20 08:10 UTC by cshao
Modified: 2022-04-16 09:05 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1322783 (view as bug list)
Environment:
Last Closed: 2016-06-08 13:03:12 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
network-he (36.80 KB, image/png)
2016-01-20 08:10 UTC, cshao 		no flags Details
new-he-network (36.92 KB, image/png)
2016-01-27 10:06 UTC, cshao 		no flags Details
/var/log/*.* + sosreport (13.37 MB, application/x-gzip)
2016-01-27 10:11 UTC, cshao 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-45720 0 None None None 2022-04-16 09:05:21 UTC
oVirt gerrit 53684 0 master MERGED Bridge.slave_for_nic needs to exclude vnet devices 2016-03-30 11:04:48 UTC
oVirt gerrit 55486 0 ovirt-3.6 MERGED Bridge.slave_for_nic needs to exclude vnet devices 2016-03-30 17:48:33 UTC

Description cshao 2016-01-20 08:10:51 UTC 
Created attachment 1116545 [details]
network-he

Description of problem:
Network status shows "Unknown ovirtmgmt" after register to rhevm3.6 with HE configured, 

Version-Release number of selected component (if applicable):
rhev-hypervisor7-7.2-20160113.0
ovirt-node-3.6.1-3.0.el7ev.noarch
ovirt-node-plugin-hosted-engine-0.3.0-6.el7ev.noarch
ovirt-hosted-engine-setup-1.3.2.2-2.el7ev.noarch
ovirt-hosted-engine-ha-1.3.3.7-1.el7ev.noarch
ovirt-node-plugin-vdsm-0.6.1-5.el7ev.noarch
hevm-appliance-20151216.0-1.3.6.ova

How reproducible:
100%

Steps to Reproduce:
1. TUI clean install rhevh
2. Login rhevh, setup network via dhcp
3. Configure Hosted engine with correct steps.
4. Reboot host.
5. Focus on network status.

Actual results:
Network status shows "Unknown ovirtmgmt" after register to rhevm3.6 with HE configured, 

Expected results:
It should show "Networking: Connected ovirtmgmt" in status page. 

Additional info:
No such issue if register to RHEV-M directly.
Comment 2 Huijuan Zhao 2016-01-22 03:19:25 UTC 
Version-Release number of selected component (if applicable):
rhev-hypervisor7-7.2-20160120.0
ovirt-node-3.6.1-3.0.el7ev.noarch
ovirt-node-plugin-hosted-engine-0.3.0-6.el7ev.noarch
ovirt-hosted-engine-setup-1.3.2.3-1.el7ev.noarch
ovirt-hosted-engine-ha-1.3.3.7-1.el7ev.noarch
ovirt-node-plugin-vdsm-0.6.1-6.el7ev.noarch
rhevm-appliance-20160120.0-1.3.6.ova


Steps to Reproduce:
1. TUI clean install rhevh
2. Login rhevh, setup network via dhcp
3. Configure Hosted engine with correct steps.
4. Reboot host.
5. Focus on network status.

Test results:
Network status shows "Networking: Connected ovirtmgmt" in status page. configured, 

So this bug is fixed in rhev-hypervisor7-7.2-20160120.0 and rhevm-appliance-20160120.0-1.3.6.ova, when the bug status is ON_QA, we can verify it directly.
Comment 3 cshao 2016-01-27 10:04:59 UTC 
I have to re-open this bug due to I met this issue twice today.
1. One nic env can reproduce.
2. Bond+vlan env can reproduce.

Test version:
rhev-hypervisor7-7.2-20160126.0
ovirt-node-3.6.1-5.0.el7ev.noarch
ovirt-node-plugin-hosted-engine-0.3.0-6.el7ev.noarch
ovirt-hosted-engine-setup-1.3.2.3-1.el7ev.noarch
ovirt-hosted-engine-ha-1.3.3.7-1.el7ev.noarch
RHEV-appliance-20160120.0-1.3.6.ova  

Test steps:
1. TUI clean install rhevh
2. Login rhevh, setup network via dhcp
3. Configure Hosted engine with correct steps.
4. Reboot host.
5. Focus on network status.

Actual results:
Network status shows "Unknown ovirtmgmt" after register to rhevm3.6 with HE configured, 

Expected results:
It should show "Networking: Connected ovirtmgmt" in status page.
Comment 4 cshao 2016-01-27 10:06:28 UTC 
Created attachment 1118731 [details]
new-he-network
Comment 5 cshao 2016-01-27 10:11:05 UTC 
Created attachment 1118746 [details]
/var/log/*.* + sosreport
Comment 6 Fabian Deutsch 2016-01-27 12:53:06 UTC 
Is the network page correct if you got to the RHEV-M page and back to the status page?
Comment 7 cshao 2016-01-28 02:31:49 UTC 
(In reply to Fabian Deutsch from comment #6)
> Is the network page correct if you got to the RHEV-M page and back to the
> status page?

No, it still show "Networking: unknown ovirtmgmt" after got to the RHEV-M page and back to the status page.
Comment 9 Ryan Barry 2016-02-03 18:42:33 UTC 
(In reply to shaochen from comment #3)
> I have to re-open this bug due to I met this issue twice today.
> 1. One nic env can reproduce.
> 2. Bond+vlan env can reproduce.
> 
> Test version:
> rhev-hypervisor7-7.2-20160126.0
> ovirt-node-3.6.1-5.0.el7ev.noarch
> ovirt-node-plugin-hosted-engine-0.3.0-6.el7ev.noarch
> ovirt-hosted-engine-setup-1.3.2.3-1.el7ev.noarch
> ovirt-hosted-engine-ha-1.3.3.7-1.el7ev.noarch
> RHEV-appliance-20160120.0-1.3.6.ova  
> 
> Test steps:
> 1. TUI clean install rhevh
> 2. Login rhevh, setup network via dhcp
> 3. Configure Hosted engine with correct steps.
> 4. Reboot host.
> 5. Focus on network status.
> 
> Actual results:
> Network status shows "Unknown ovirtmgmt" after register to rhevm3.6 with HE
> configured, 
> 
> Expected results:
> It should show "Networking: Connected ovirtmgmt" in status page.

I tried this today with the same rhev-hypervisor image and same rhevm-appliance.

I wasn't able to reproduce it. The status page was correct both before and after rebooting.

I'll try again, but are these the exact steps taken to reproduce?
Comment 10 cshao 2016-02-13 13:36:20 UTC 
> I tried this today with the same rhev-hypervisor image and same
> rhevm-appliance.
> 
> I wasn't able to reproduce it. The status page was correct both before and
> after rebooting.
> 
> I'll try again, but are these the exact steps taken to reproduce?


Exact steps
1. TUI clean install rhevh on local machine.
2. Login rhevh, setup network via dhcp or bond+vlan.
3. Switch to HE menu
4. File the OVA URL with correct path.
5. Configure Hosted engine with correct steps(NFS type).
6. Finish HE configure.
7. Wait until register done, reboot host.
8. Focus on network status.
Comment 14 Ryan Barry 2016-02-17 23:33:44 UTC 
This appears to be a duplicate of bz#1280241

I'll look into why the original patch was reverted.

Please try to re-verify bz#1280241.

I'll see if I can rework the follow-up patch to also resolve this.
Comment 15 cshao 2016-02-24 06:00:21 UTC 
(In reply to Ryan Barry from comment #14)
> This appears to be a duplicate of bz#1280241
> 
> I'll look into why the original patch was reverted.
> 
> Please try to re-verify bz#1280241.
> 
> I'll see if I can rework the follow-up patch to also resolve this.

Done.
Details info please refer bug 1280241 #c19.
Comment 16 Mike McCune 2016-03-28 23:24:30 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 18 Fabian Deutsch 2016-06-08 13:04:16 UTC 
This bug got closed, because a code-level fix for this issue will not be available in RHEV 4.0.
But this issue will be fixed from a functional perspective, because the fix to this issue is covered by the migration to Cockpit for administration.
Note You need to log in before you can comment on or make changes to this bug.