g-s-s can leave images in broken state
Bug #1484886 reported by
Tom Haddon
This bug affects 5 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Glance-Simplestreams-Sync Charm |
Triaged
|
High
|
Unassigned | ||
| simplestreams |
New
|
Undecided
|
Unassigned | ||
| glance-simplestreams-sync (Juju Charms Collection) |
Invalid
|
High
|
Unassigned | ||
Bug Description
We had an issue earlier today where a run of glance-
http://
This left us with simplestreams data that was incorrect for the daily 14.04 amd64 image (possibly others, that was the only one we checked specifically). We fixed this by deleting the image and then rerunning g-s-s (we'd previously tried just rerunning g-s-s without deleting the image, and while there were no errors in the logs, we were still unable to juju deploy the image). Here's the diff in auto.sync.json:
http://
glance-
| tags: | added: canonical-bootstack |
Revision history for this message
| James Troup (elmo) wrote | #1 |
| no longer affects: | glance-simplestreams-sync-charm |
| Changed in glance-simplestreams-sync (Juju Charms Collection): | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in charm-glance-simplestreams-sync: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in glance-simplestreams-sync (Juju Charms Collection): | |
| status: | Triaged → Invalid |
To post a comment you must log in.
So the fundamental bug here, IMO, is that g-ss-s will happily replace a functional simplestreams index with a broken one. Specifically, it's writing out images without an "arch" value. It should never do this because when it does juju ignores them and then proceeds to break in wonderfully obscure ways that's an incredible headache to debug.
IMO, it should have the concept of 'required' key/values for images and not update/add new images which are missing them and obviously "arch" should be one of these.