It’s bug https://bugzilla.redhat.com/show_bug.cgi?id=1676893, fixed in vdsm-4.30.12-1 which will be in 4.3.3.

In my experience, it’s generally safe to restart vdsmd. One of those things I wouldn’t do all the time, of course, but generally safe.

On Apr 14, 2019, at 4:00 PM, Strahil Nikolov <hunter86_bg@yahoo.com> wrote:

As I couldn't find the exact mail thread, I'm attaching my /usr/lib/python2.7/site-packages/vdsm/virt/guestagent.py which fixes the missing/wrong status of VMs.

You will need to restart vdsmd (I'm not sure how safe is that with running guests) in order to start working.

Best Regards,
Strahil Nikolov
<guestagent.py>_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KK4NVC3U37HPKCO4KPO4YRBFCKYPDRGE/