Built vm image file retains random temp filename
Bug #568687 reported by
Marcus Bointon
This bug affects 7 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Server papercuts |
New
|
Undecided
|
Unassigned | ||
vm-builder (Ubuntu) |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
This is just a small feature request. While vmbuilder is running, it constructs the new VM in /tmp under a randomly generated folder name like 'tmpkJv90L'. When it's finished, it moves the completed image file to the location given by the --dest option, however, it retains the cryptic folder name as the filename for the image file. So for example if I specified --dest /home/me/webserver --hostname webserver and I end up with a folder containing run.sh and an image file called tmpkJv9OL.qcow2. It would be nicer and easier to manage if it called it webserver.qcow2, possibly appending numbers or letters to deal with filename clashes.
Changed in vm-builder (Ubuntu): | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
summary: |
- Bulit vm image file retains random temp filename + Built vm image file retains random temp filename |
To post a comment you must log in.
Indeed, vmbuilder under Lucid keeps the temporary name.
Because of this, automated scripts that look for disk0.qcow2 or so, fail.
Of course, we can work around it, but I'd like to see clear names again.
It is difficult to identify the correct image now when vmbuilder creates several disk images.