Needs better logging so we can run image server on production envs
Bug #1430853 reported by
Caio Begotti
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu system image |
Fix Committed
|
Undecided
|
Caio Begotti |
Bug Description
Right now it's nearly impossible to know what's going on with image server when importing and processing images, either via a cron job or something else, because it does not print much useful information.
The ideal is to have enough info or debug messages printed to the console so we can run image server remotely without having to ssh into its machine to provide manual support ourselves.
Related branches
lp://staging/~caio1982/ubuntu-system-image/sis-logging
- Stéphane Graber (community): Needs Fixing
-
Diff: 574 lines (+101/-17)4 files modifiedlib/systemimage/generators.py (+71/-9)
lib/systemimage/gpg.py (+6/-1)
lib/systemimage/tools.py (+17/-6)
lib/systemimage/tree.py (+7/-1)
Changed in ubuntu-system-image: | |
assignee: | nobody → Caio Begotti (caio1982) |
status: | New → Fix Committed |
To post a comment you must log in.
The related branch I just added address part of this problem for me.