Well, today is Oct 8th 2014 and I just lost three VMs because of this.
That the tyrget folder (/var/lib/libvirt/images) wasn't backed-up is my
fault but the documentation SHOULD BE CLEARER about what happens when
you pass the -o option to vmbuilder.
And yes, overwriting the whole directory is
** Also affects: vmbuilder
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/1090223
Title:
The directory ubuntu-kvm disappeared after
Today is the 10th of december 2013.
This bug on 2012-12-14 has been marked as High importance and no bugfix has
been released.
Today I've lost a virtual machine in my production enviroment using che
-o option.
This is really frustrating.
--
You received this bug notification because you are
** Changed in: vm-builder (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in Ubuntu.
https://bugs.launchpad.net/bugs/1090223
Title:
The directory ubuntu-kvm disappeared after
Hi Robie, I'd like to help to report bugs or fixing bugs.
Back to the beginning of this problem, if vmbuilder didn't create a directory
containing a single VM image, users won't put other VM images in the directory.
So is it really necessary to have a directory? IMHO maybe just a VM image is
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It sounds to that at the very least the documentation could be made
clearer here. So at the minimum, this could be a documentation bug that
could lead to data loss, so marking this as Importance: High.
** Changed
Sorry, it should not be a bug, but a misleading option.
According to the official virtualization guide:
http://doc.ubuntu.com/ubuntu/serverguide/C/jeos-and-vmbuilder.html
the -o tells vmbuilder to overwrite the previous version of the VM
The users should suppose to overwrite ONLY the VM.
But the
