Images added through objectstore and EC2 RegisterImage are never made available to the OpenStack API
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
High
|
Vish Ishaya | ||
Bug Description
In nova/image/s3.py, we pull the image out of nova-objectstore, decrypt it, and put it into the real image service (e.g. glance). Along the way, we set a custom image property image_state a couple of times to track the progress in this process. This is because glance (rightfully!) has fewer states (active, killed, queued, and saving). Once this process is completed, image_state is set to "available".
The EC2 api knows about this extra state and so knows when the image is ready. However, the OpenStack API does not. It relies exclusively on the "status" attribute of the image.
We should use image_state only to track the intermediate states of the image. Once the image is "available", it shoudl be marked "active" and the image_state is obsolete and can be dropped.
Related branches
- Ed Leafe (community): Approve
- Trey Morris (community): Approve
- Devin Carlen (community): Approve
-
Diff: 128 lines (+68/-26)1 file modifiednova/image/s3.py (+68/-26)
| Vish Ishaya (vishvananda) wrote | #1 |
| Changed in nova: | |
| assignee: | Soren Hansen (soren) → Vish Ishaya (vishvananda) |
| importance: | Undecided → High |
| status: | Triaged → In Progress |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → diablo-1 |
| Changed in nova: | |
| milestone: | diablo-1 → 2011.3 |
| status: | Fix Committed → Fix Released |
I actually fixed this as part of my branch here:
https:/