<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sun, May 11, 2014 at 8:18 PM, Gianluca Cecchi <span dir="ltr"><<a href="mailto:gianluca.cecchi@gmail.com" target="_blank">gianluca.cecchi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class=""><div class="gmail_extra"><div class="gmail_quote">On Sun, May 11, 2014 at 4:10 PM, Roy Golan <span dir="ltr"><<a href="mailto:rgolan@redhat.com" target="_blank">rgolan@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><br>
The vm will stay in "Waiting.." as the getVdsCaps is failing and the
monitoring of Vms will not take place.<br>
need to fix this "Unexpected error" first. is it a matter of ssl
enabled configuration for host communication? i.e. can you try
vdsClient -s 0 getVdsCaps ?<br>
<br>
</div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank">http://lists.ovirt.org/mailman/listinfo/users</a><br>
<br></blockquote></div><br><br></div></div><div class="gmail_extra">I didn't change anything on this server.<br>It is an all-in-one config so both engine and vdsm host are on it.<br></div><div class="gmail_extra">Yesterday and every previous day I was able to start the system and start the VM; I only applied the yum update command yeseterday<br>
</div><div class="gmail_extra">(with --exclude=sos due to the opened bug) and then I made shutdown of the system.<br></div><div class="gmail_extra">Today after startup I got this problem.<br><br>[root@tekkaman vdsm]# vdsClient -s 0 getVdsCaps<br>
Unexpected exception<br><br></div><div class="gmail_extra">it seems the error in vdsm.log when I run the command above is of this type:<br><br>Thread-25::ERROR::2014-05-11 20:18:02,202::BindingXMLRPC::1086::vds::(wrapper) unexpected error<br>
Traceback (most recent call last):<br> File "/usr/share/vdsm/BindingXMLRPC.py", line 1070, in wrapper<br> res = f(*args, **kwargs)<br> File "/usr/share/vdsm/BindingXMLRPC.py", line 393, in getCapabilities<br>
ret = api.getCapabilities()<br> File "/usr/share/vdsm/API.py", line 1185, in getCapabilities<br> c = caps.get()<br> File "/usr/share/vdsm/caps.py", line 369, in get<br> caps.update(netinfo.get())<br>
File "/usr/lib64/python2.7/site-packages/vdsm/netinfo.py", line 557, in get<br> netAttr.get('qosOutbound'))<br> File "/usr/lib64/python2.7/site-packages/vdsm/netinfo.py", line 487, in _getNetInfo<br>
ipv4addr, ipv4netmask, ipv6addrs = getIpInfo(iface)<br> File "/usr/lib64/python2.7/site-packages/vdsm/netinfo.py", line 317, in getIpInfo<br> ipv6addrs = devInfo.get_ipv6_addresses()<br>SystemError: error return without exception set<br>
<br></div></div>
</blockquote></div><br>Based on above errors, I think that for some reason these two python related packages that were updated yesterday are causing some problems with vdsm.<br>Can you confirm that you can run ok the 3.4 vdsm with those?<br>
<br>vdsm-4.14.6-0.fc19.x86_64<br><br>May 10 21:24:23 Updated: python-ethtool-0.9-2.fc19.x86_64<br>May 10 21:24:23 Updated: python-lxml-3.3.5-1.fc19.x86_64<br><br></div><div class="gmail_extra">I can also try to rollback and see...<br>
<br></div></div>