[rfe] implement fsfreeze retry when creating snapshot

Bug #2023162 reported by Soroush Kaviani
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Confirmed
Undecided
Unassigned

Bug Description

Hello
When i create snapshot from some of my instances with Windows OS the snapshot is deleted from list and when I check the nova compute log i see this error:

Nov 29 09:37:32 computeXX libvirtd[2880]: internal error: unable to execute QEMU agent command 'guest-fsfreeze-thaw': couldn't hold writes: fsfreeze is limited up to 10 seconds:

Qemu Guest Agent version in windows instances are updated but problem not solved.
now the only way to create snapshot from these instances is pausing and then create snapshot.

I have send guest-fs-freeze command manually to instance and i see sometime freezing maybe timed_out but if the fs-freeze request be repeated fs-freeze is done with success.

I think if nova repeats the fs_freeze request to qemu-guest-agent of instances when get timeout, the problem solve and live snapshot for all windows instances is without any problem.

thanks for your attention

Tags: rfe
Revision history for this message
Balazs Gibizer (balazs-gibizer) wrote :

This feels like a small feature request. The best would be to be able to pass a timeout parameter from nova to libvirt then nova can make the timeout configurable. As far as I see libvirt does not provide such parameter[1]. So yes the other option is to implement a retry loop on the nova-compute side. If you have the motivation to push this small feature forward then I suggest to show up on #openstack-nova IRC channel (on OFTC) to discuss this forward.

Marking this as valid as an rfe

[1] https://libvirt.org/html/libvirt-libvirt-domain.html#virDomainFSFreeze
[2] https://wiki.openstack.org/wiki/Meetings/Nova

tags: added: rfe
Changed in nova:
status: New → Confirmed
summary: - fsfreeze error when create snapshot windows instances
+ [rfe] implement fsfreeze retry when creating snapshot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.