"uvt-simplestreams-libvirt sync" remove running virtual's image

Bug #1501586 reported by yochaos
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
uvtool
Confirmed
High
Unassigned

Bug Description

On my system, I use /vir/images as storage pool instead of /var/lib/uvtool/libvirt/images by "virsh pool-edit uvtool".
...
<target>
    <path>/virt/images</path>
    <permissions>
         <mode>0700</mode>
         <owner>-1</owner>
         <group>-1</group>
    </permissions>
</target>
....

Steps:
1. uvt-simplestreams-libvirt sync release=vivid arch=amd64
2. uvt-kvm create firsttest release=vivid
3. firsttest-ds.qcow and firsttest.qcow are created under /virt/images, and it is running smoothly.
4. uvt-simplestreams-libvirt sync release=trusty arch=amd64
5. firsttest-ds.qcow and firsttest.qcow are removed from /virt/images.

Version info:
Ubuntu 15.04
uvtool-libvirt 0~bzr99-0ubuntu1
libvirt-bin 1.2.12-0ubuntu14.2
libvirt0 1.2.12-0ubuntu14.2
python-libvirt 1.2.12-0ubuntu1

Revision history for this message
Robie Basak (racb) wrote :

Thank you for reporting this bug.

Yes, handling a storage pool in a different location doesn't work well at the moment. Bug 1289784 is a related (but different) issue.

Changed in uvtool:
importance: Undecided → High
Benoy George (bge007)
Changed in uvtool:
status: New → Confirmed
Revision history for this message
Eric Heydrick (eheydrick) wrote :

Got bit by this. It also seems to delete the backing store image. Is there a way to store images in a non-standard location?

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.