Cinder

Handle terminate_connection() exception in Force Detach Volume API

Bug #1265158 reported by ling-yun
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Cinder
Invalid
Undecided
Unassigned

Bug Description

It's possile that backend drivers throw exceptions while doing terminate_connection operation. Currently exceptions are bubbled up to Force Detach Volume API not being handled. This patch logs exception in Force Detach Volume API and then raises VolumeBackendAPIException to caller.

See original description
ling-yun (zengyunling)
Changed in cinder:
assignee: nobody → ling-yun (zengyunling)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.openstack.org/64515

Changed in cinder:
status: New → In Progress
Revision history for this message
Lihi Tikolsky (lihit) wrote :

If the backend driver fails to perform the 'detach' action, it raises an exception. In this scenarion, the volume will be stack in 'detaching' state forever.
For example:
There is no connectivity to the storage while the action is performed and the volume is now in 'detaching' state.
After a short while connectivity is back, but the volume is stuck in that state

I believe this issue should be addressed.

Revision history for this message
Sean McGinnis (sean-mcginnis) wrote :

Automatically unassigning due to inactivity.

Changed in cinder:
assignee: ling-yun (zengyunling) → nobody
status: In Progress → Triaged
Revision history for this message
Sean McGinnis (sean-mcginnis) wrote :

I don't believe this is an issue anymore and we are able to work around failures better than when this was filed.

Changed in cinder:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.