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):
Steps to Reproduce:
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.
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.
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.
In my patch should be hotplugged devices visible in vdsStats after 10 seconds after devices are plugged.
set verified by mistake, putting back to ON_QA
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.