Comment 2 for bug 2009849

I re-created the snapshot manually (see info below) but the issue persists.

[root@phoenix ea003e1a1bee1aaf573aafc40cd188ff]# qemu-img info volume-e67af022-0d5b-4253-9981-c8b34622e058.3df6ef28-7f8d-45bc-a9e2-d67703c020ae
image: volume-e67af022-0d5b-4253-9981-c8b34622e058.3df6ef28-7f8d-45bc-a9e2-d67703c020ae
file format: qcow2
virtual size: 1 GiB (1073741824 bytes)
disk size: 196 KiB
cluster_size: 65536
backing file: volume-e67af022-0d5b-4253-9981-c8b34622e058
backing file format: qcow2
Format specific information:
    compat: 1.1
    compression type: zlib
    lazy refcounts: false
    refcount bits: 16
    corrupt: false
    extended l2: false
[root@phoenix ea003e1a1bee1aaf573aafc40cd188ff]#

I created this snapshot from a volume attached to a VM while the vm was shutdown. Openstack would not still not allow the operation while the volume is attached so I used the "force" switch via Horizon. Since then the VM has been deleted. The creation of new snapshots from the same volume also fails, but I can remove the failed snapshots.
Maybe worth to mention: my setup is a all-in-one setup, manually installed; no ansible involved. Cinder is configured to use the NFS backend, where the NFS server is also hosted in the same machine.