Unquiesce an Instance after a Failed Volume Snapshot

Registered by Eric M Gonzalez

During "snapshot_volume_backed()" an instance is quiesced ( fsfreeze ) before all attached volumes are iterated and a snapshot request sent to Cinder. If Cinder cannot complete a snapshot it will raise an exception. The function "snapshot_volume_backed()" does not catch this exception and the instance is never thawed. This leaves the instance in a frozen, read-only, inconsistent state until the filesystem can be thawed.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Eric M Gonzalez
Direction:
Needs approval
Assignee:
Eric M Gonzalez
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Matt Riedemann

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bug/1731986,n,z

Addressed by: https://review.openstack.org/519464
    unquiesce instance on volume snapshot failure

Marked as Obsolete. Blueprints are for features, this is fixed via bug 1731986.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.