Change the handling for volume operation timeouts.

Registered by Tobias Engelbert

While performing multiple volume operations on a storage backend array, a timeout can occur, e.g. during an attach volume operation. In that case nova stops the attach volume attempt and sets it status back to available, but the operation might continue on the backend array which causes inconsistencies between the database in cinder and the backend array. This blueprint proposes a solution for this.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Tobias Engelbert
Direction:
Needs approval
Assignee:
Tobias Engelbert
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Sean McGinnis

Related branches

Sprints

Whiteboard

(smcginnis): Marking obsolete as this has been sitting out there for a long time. If this is still needed, please submit a new bp.

https://review.openstack.org/#/c/132225/

Gerrit topic: https://review.openstack.org/#q,topic:bp/volume-status-polling,n,z

Addressed by: https://review.openstack.org/154377
    Recall mechanism for terminate/initialize

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.