Bug 1272954 - glusterFS_native_driver: snapshot delete doesn't delete snapshot entries that are in error state
glusterFS_native_driver: snapshot delete doesn't delete snapshot entries that...
Status: CLOSED UPSTREAM
Product: RDO
Classification: Community
Component: openstack-manila (Show other bugs)
Liberty
Unspecified Unspecified
unspecified Severity high
: ---
: Kilo
Assigned To: Pete Zaitcev
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-19 05:56 EDT by krishnaram Karthick
Modified: 2015-11-23 18:16 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-23 18:16:45 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description krishnaram Karthick 2015-10-19 05:56:24 EDT
Description of problem:

In openstack-manila running Liberty release, if snapshot creation fails for some reason, an entry for snapshot is still created with 'error' state. Attempting to delete this invalid entry of snapshot doesn't succeed.

Possible scenarios which could create a snapshot in error state are when,

 - gluster daemon is down in the backend gluster node
 - gluster node is down
 - gluster brick process is down
 - gluster volume is down
 - snapshot created by manila is deleted from backend gluster

While it is okay to create a snapshot with error state, attempting to delete or force-delete should clear the entry from database. Administrator has no means to remove these snapshots in error state.

Version-Release number of selected component (if applicable):


# rpm -qa | grep 'manila'
python-manila-1.0.0.0-rc2.dev24.el7.centos.noarch
python-manilaclient-1.4.1-dev3.el7.centos.noarch
openstack-manila-1.0.0.0-rc2.dev24.el7.centos.noarch
openstack-manila-share-1.0.0.0-rc2.dev24.el7.centos.noarch


How reproducible:
Always

Steps to Reproduce:

1) Try to create a snapshot when volume is down (one of the possible ways to create a snapshot that would end up in error state)
2) A snapshot in error state is created
3) Attempt to delete or force-delete the snapshot - Snapshot doesn't gets deleted

Actual results:
# manila snapshot-list
+--------------------------------------+--------------------------------------+--------+---------+------------+
| ID | Share ID | Status | Name | Share Size |
+--------------------------------------+--------------------------------------+--------+---------+------------+
| fac9835a-9689-46a0-8ee7-d2f2d12ad486 | 68c37e73-9710-430a-8f39-7d79ad6af669 | error | snap-01 | 1 |
+--------------------------------------+--------------------------------------+--------+---------+------------+
# manila snapshot-delete fac9835a-9689-46a0-8ee7-d2f2d12ad486
# manila snapshot-list
+--------------------------------------+--------------------------------------+----------------+---------+------------+
| ID | Share ID | Status | Name | Share Size |
+--------------------------------------+--------------------------------------+----------------+---------+------------+
| fac9835a-9689-46a0-8ee7-d2f2d12ad486 | 68c37e73-9710-430a-8f39-7d79ad6af669 | error_deleting | snap-01 | 1 |
+--------------------------------------+--------------------------------------+----------------+---------+------------+

Expected results:
snapshot in error state is deleted successfully

Additional info:

Note You need to log in before you can comment on or make changes to this bug.