Bug 1311151 - [Hosted-engine] - The vNIC(vnet0) of the HostedEngine VM reported as unplugged in UI although it is actually UP in the guest
Summary: [Hosted-engine] - The vNIC(vnet0) of the HostedEngine VM reported as unplugge...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.HostedEngine
Version: ---
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ovirt-3.6.6
: 3.6.6
Assignee: Jenny Tokar
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-23 13:57 UTC by Michael Burman
Modified: 2019-11-14 07:29 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: When a vm was imported the nic was imported with a generated id instead of the id that was reported by the vm. Consequence: When monitoring the vm the imported nic was not recognized and it's status was set to unplugged. Fix: Import the nic with the id that is reported by the vm. Result: The nic is reported as up in the UI.
Clone Of:
Environment:
Last Closed: 2016-05-30 10:51:51 UTC
oVirt Team: SLA
Embargoed:
rule-engine: ovirt-3.6.z+
ylavi: planning_ack+
rgolan: devel_ack+
rule-engine: testing_ack+


Attachments (Terms of Use)
logs+screenshots (359.46 KB, application/x-gzip)
2016-02-23 13:57 UTC, Michael Burman
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1312730 0 unspecified CLOSED [Hosted-engine] - The vNIC(vnet0) of the HostedEngine VM is not reported and shown in the UI 2021-02-22 00:41:40 UTC
oVirt gerrit 55214 0 'None' 'MERGED' 'HE: fixed the vm nic changing it''s status to unplugged.' 2019-11-14 07:56:20 UTC
oVirt gerrit 55290 0 'None' 'MERGED' 'HE: fixed the vm nic changing it''s status to unplugged.' 2019-11-14 07:56:20 UTC

Internal Links: 1312730

Description Michael Burman 2016-02-23 13:57:21 UTC
Created attachment 1129767 [details]
logs+screenshots

Description of problem:
[Hosted-engine] - The vNIC(vnet0) of the HostedEngine VM reported as unplugged in UI although it is actually UP in the guest.

- Once finishing the hosted-engine deployment and entering the web admin, we need to create a master storage domain in order to import the hosted engine storage domain to the setup and to see the HostedEngine VM in the UI(Virtual Machines main tab).
Once the HostedEngine VM is UP, the vNIC(vnet0) reported and displayed as unplugged, although it is actually UP in the guest and VM have ip over this vNIC.

[root@network-hosted-engine-vlan162-3 ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:1a:4a:16:24:64 brd ff:ff:ff:ff:ff:ff
    inet 10.35.129.16/24 brd 10.35.129.255 scope global eth0
    inet6 2620:52:0:2381:21a:4aff:fe16:2464/64 scope global dynamic 
       valid_lft 2591925sec preferred_lft 604725sec
    inet6 fe80::21a:4aff:fe16:2464/64 scope link 
       valid_lft forever preferred_lft forever


Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup-1.3.3.3-1.el7ev.noarch

How reproducible:
100

Steps to Reproduce:
1. Run hosted-engine --deploy on rhel 7.2 latest 3.6 
2. Finish deployment and enter the web admin(UI)  
3. Create master storage domain and wait for the hosted storage domain to be imported to the setup and to the HostedEngine VM to be UP. 
4. Check the vNIC(vnet0) in UI and in guest(vnc or ssh)

Actual results:
vNIC reported as linked but not plugged in UI.
In guest it is UP.

Expected results:
The vNIC(vnet0) of the HostedEngine VM should be reported and displayed as plugged in the UI.

Comment 1 Martin Sivák 2016-02-24 14:09:53 UTC
I believe this is network reporting issue, hosted engine got you to step 3 (the VM is UP and the engine is responding) properly. Network reporting then should have nothing to do with it.

Can you please check what the host running the VM reports in getVdsCapabilities and getAllVmStats? (vdsClient -s 0 <command>).

We need someone from networking to tell us how the plugged flag gets to the engine here.

Comment 2 Michael Burman 2016-02-24 14:26:30 UTC
Hi Martin, i don't have this setup any more, sorry.

I just finished talking with rgolan and he is aware of that and that is an easy fix. I'm not sure if it's should be a Network or SLA fix.

Comment 3 Dan Kenigsberg 2016-03-02 09:29:28 UTC
Dotan, is that the case in your recently-installed hosted-engine?

Comment 4 Dan Kenigsberg 2016-03-06 15:05:58 UTC
I can confirm that this is the case with

ovirt-hosted-engine-setup-1.3.3.4-1.fc22.noarch
ovirt-engine-3.6.3.4-1.el7.centos.noarch

HEimport should setPlugged for all interfaces that are reported by Vdsm.

Comment 5 Mike McCune 2016-03-28 22:50:27 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 6 Michael Burman 2016-04-28 08:54:45 UTC
Verified on - rhevm-3.6.6-0.1.el6.noarch with 
ovirt-hosted-engine-setup-1.3.6.0-1.el7ev.noarch
rhevm-appliance-20160428.0-1.x86_64.rhevm.ova
vdsm-4.17.27-0.el7ev.noarch


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