[sheepdog-users] Sheep crashes when cloning via qemu non empty snapshots

[Ing. Luca Lazzeroni - Trend Servizi Srl]

Hi,
I've found a repeatable (in my configuration) problem with snapshots and cloning.

Cluster made of 3 machines. Latest master git release of sheepdog. 

Make a snapshot of a vdi via qemu-img => success.
Do some works on vm backed by snapshot volume => success.
Trying to create a clone starting from snapshot with qemu-img (version 1.5.0)

qemu-img create -b sheepdog:TestVDI:1 NewVDI

 => crash of sheep with this errors:

Jun 27 14:42:17 [oc_push 31674] push_cache_object(532) failed to push object Object is read-only
Jun 27 14:42:17 [oc_push 31674] do_push_object(897) PANIC: push failed but should never fail
Jun 27 14:42:17 [oc_push 31674] crash_handler(181) sheep exits unexpectedly (Aborted).
Jun 27 14:42:17 [oc_push 31676] push_cache_object(532) failed to push object Object is read-only
Jun 27 14:42:17 [oc_push 31676] do_push_object(897) PANIC: push failed but should never fail
Jun 27 14:42:17 [oc_push 31239] push_cache_object(532) failed to push object Object is read-only
Jun 27 14:42:17 [main] crash_handler(487) sheep pid 31226 exited unexpectedly.

Every time I try to make the clone using qemu-img => same result.

Trying to clone the vdi using "collie vdi clone -s TestVDISnapshot TestVDI NewVDI" => success.

It seems there's somethink broken in qemu-img managing clone from snapshot with cache enabled.
Note that the VM is powered OFF when I try to make the clone, so its cache should be empty..

Thank you, 

Luca