PureISCSIDriver sends volume into "Error_Deleting" state during "delete_volume" operation if volume already deleted

Bug #1395826 reported by Mudassir Latif
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Undecided
Mudassir Latif

Bug Description

In cases where the volume is deleted directly without using Horizon or any other OpenStack tool (Note: not recommended). OpenStack becomes out of sync with reality. An operation to delete the volume results in array returning "Volume does not exist" error.
The driver should discriminate between other general errors and "Volume does not exist" error and treat the volume as deleted successfully.

Tags: drivers pure
tags: added: cinder pure
tags: added: driver
Changed in cinder:
assignee: nobody → Mudassir Latif (mudassir-latif)
Mike Perez (thingee)
tags: added: drivers
removed: cinder driver
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/136954

Changed in cinder:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/136954
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=0d47799beaad6fb390c4761fef8d84d665f9b189
Submitter: Jenkins
Branch: master

commit 0d47799beaad6fb390c4761fef8d84d665f9b189
Author: Mudassir Latif <email address hidden>
Date: Mon Nov 24 19:00:47 2014 -0800

    PureISCSIDriver:Handle delete called on already deleted volume

    If the delete_volume method gets an error from Purity
    saying volume does not exist, don't proceed with attempt
    at deletion

    Change-Id: I2a830e43c876433da4cdb50eabe4fb66b7eb6faf
    Closes-Bug: #1395826

Changed in cinder:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in cinder:
milestone: none → kilo-1
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in cinder:
milestone: kilo-1 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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