Instance stuck in task state image_snapshot
Bug #1101136 reported by
Julie Pichon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Medium
|
Eoghan Glynn | ||
Folsom |
Fix Released
|
Medium
|
Eoghan Glynn |
Bug Description
This is happening in a Folsom environment.
I tried to create a snapshot of a running instance, and got a message back from Horizon reading "Unable to create snapshot" because the administrator had recently changed snapshotting/image creation to be an admin-only action.
Since then, my instance Task State is stuck in OS-EXT-
Steps to reproduce:
1. Update the Glance policy file with "add_image": [["role:admin"]]
2. Attempt to create a snapshot
Expected result:
3. Snapshot fails and the instance returns to a normal active state
Actual result:
4. Snapshot fails and the instance task state stays in "image_snapshot"
tags: | added: folsom-backport-potential |
tags: | removed: folsom-backport-potential |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-3 → 2013.1 |
To post a comment you must log in.
The problem is that the task state reversion logic *only* kicks in if the failure occurs on the compute node.
Whereas in this case, an eager attempt is made to create the image upfront from the API node, before even casting the snapshot_instance RPC to the compute node.
This upfront image creation fails with 403 because of the RBAC settings, but the task state is never reverted.