Image server should not wipe imported images by default, nor its publish_path
Bug #1430871 reported by
Caio Begotti
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu system image |
New
|
Undecided
|
Unassigned |
Bug Description
Currently the image server code wipes out all images after they have been processed from copy-images or import-images, which IMHO is plainly wrong. Removing files should be optional, not default, as image server may be sitting next to a storage or archiver of phone images (like we do on Prodstack).
Also, by doing so it wipes out its own publish_path too, so it may render next runs of import-images broken:
Traceback (most recent call last):
File "bin/import-
pub = tree.Tree(conf)
File "/tmp/system-
raise Exception("Invalid path: %s" % path)
Related branches
lp:~caio1982/ubuntu-system-image/sis-nondestructive
On hold
for merging
into
lp:ubuntu-system-image/server
- Stéphane Graber (community): Needs Fixing
-
Diff: 63 lines (+13/-4)3 files modifiedbin/copy-image (+5/-2)
bin/import-images (+5/-2)
lib/systemimage/tree.py (+3/-0)
To post a comment you must log in.
The related branch solves this problems for us while also keeps the original behavior available through a command line option in both copy and import images scripts.