I can't write an elaborate response since I am away from my laptop, but a workaround would be to simply insert the snapshot back to the snapshots table

You need to locate the snapshot's id in the logs where the failure occured and use vm's id

insert into snapshots values ('<snapshot uuid>', '<vm uuid>', 'ACTIVE', 'OK', 'Active VM', '2018-02-21 14:00:11.845-04'

On Thu, 19 Jul 2018, 14:48 , <pwightm@gmail.com> wrote:

I've hit the issue described in:
https://access.redhat.com/solutions/3393181
https://bugzilla.redhat.com/show_bug.cgi?id=1561052

I have one VM with three disks that cannot start. Logs indicate a null pointer exception when trying to locate the snapshot. I've verified in the engine db that no "Active" snapshot exists for the VM (this can also be seen in the WebUI).

oVirt hosts and engine are both (now) on RHEL7.5. Not sure if this snapshot failed to create before the hosts were updated to 7.5 - the VM in question is a server that never gets shutdown but rather is migrated around while we perform host maintenance.

oVirt: v4.2.1.7-1

Host:
kernel: 3.10.0-862.9.1
KVM: 2.9.0-16
libvirt: libvirt-3.9.0-14.el7_5.6
VDSM: vdsm-4.20.27.1-1

The article just says to contact RH support, but I don't have a RHEV support agreement for my oVirt cluster. Anyone know how to recover this VM?
_______________________________________________
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/ORFFAFL5G2JDBJXAQKNBBTKJGGBRD636/