Bug 988469 - PRD34 - [RFE] vdsm does not recognize hot-plugged host interfaces
PRD34 - [RFE] vdsm does not recognize hot-plugged host interfaces
Status: CLOSED ERRATA
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm (Show other bugs)
3.2.0
All Linux
medium Severity medium
: ---
: 3.4.0
Assigned To: Dan Kenigsberg
Martin Pavlik
network
: FutureFeature
Depends On: 1240719 999947
Blocks: 1058499 rhev3.4beta 1142926
  Show dependency treegraph
 
Reported: 2013-07-25 12:13 EDT by Pratik Pravin Bandarkar
Modified: 2016-02-10 14:51 EST (History)
10 users (show)

See Also:
Fixed In Version: ovirt-3.4.0-alpha1
Doc Type: Enhancement
Doc Text:
VDSM now recognizes hot-plugged host interfaces.
Story Points: ---
Clone Of:
: 1058499 (view as bug list)
Environment:
Last Closed: 2014-06-09 09:25:10 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Network
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
nyechiel: Triaged+


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 16227 None None None Never

  None (edit)
Description Pratik Pravin Bandarkar 2013-07-25 12:13:18 EDT
Description of problem:
While system bootup, for some reason network interface was not detected. This issue got resolved after some time. ethtool <ethX> / ifconfig was showing the interface. But,  still "getVdsStats" output was not detecting the interface and as a result, vdsm was assuming the interface is not present on the system. As a workaround we manually restarted the "vdsmd" service. Then, it(vdsm) detected the interface. 


Version-Release number of selected component (if applicable):
vdsm

How reproducible:
100%

Steps to Reproduce:
1. 
2.  
3.

Actual results:
Even after network issue got resolved, "getVdsStats" output was not showing the interface and as a result, vdsm was assuming the interface is not present on the system. Manual intervention(service vdsmd restart) is needed to tell vdsm that, ethX interface is up. 

Expected results:
Once network issue is resolved and respective ethX interface detected by the system, changes should automatically reflect to vdsm. Manual intervention should not be there. 

Additional info:
Comment 1 Pratik Pravin Bandarkar 2013-07-25 12:27:53 EDT
I can reproduce the issue on nested virtulization:

1. start the hypervisor.
2. add NIC on the fly.
3. check if its detected by system from dmesg/ethtool ethX
4. Check if the same NIC gets displayed in:
---
 vdsClient -s 0 getVdsStats | egrep --color eth
---
it will not be there.

5. Now restart the vdsmd service:
6. Now you can see new interface from "vdsClient -s 0 getVdsStats" output.
Comment 2 psebek 2013-10-30 09:22:58 EDT
In my patch should be hotplugged devices visible in vdsStats after 10 seconds after devices are plugged.
Comment 11 Martin Pavlik 2014-02-24 11:09:12 EST
set verified by mistake, putting back to ON_QA
Comment 12 errata-xmlrpc 2014-06-09 09:25:10 EDT
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.

http://rhn.redhat.com/errata/RHBA-2014-0504.html

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