Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/

Bug 1049786

Summary:	openstack-cinder: failed to delete the volume in glusterFS
Product:	[Community] RDO	Reporter:	Yogev Rabl <yrabl>
Component:	openstack-cinder	Assignee:	Eric Harney <eharney>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Dafna Ron <dron>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	eharney, yeylon, yrabl
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	storage
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-02 13:07:50 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yogev Rabl 2014-01-08 08:40:16 UTC

Description of problem:
the Cinder failed to delete a volume in the GlusterFS, and the logs show that the operation was successful:

2014-01-08 10:22:41.631 7705 INFO cinder.volume.manager [req-713496ad-cbb5-439c-b5eb-7fff598480ba c2b12ec6592a4259b2e2b45b7f278150 2c398f94ad5e410bb0d8be60ddf60d84] volume 8b971
83f-4a12-4e75-9483-3af5322de07c: deleting
2014-01-08 10:22:41.633 7705 INFO cinder.volume.manager [req-713496ad-cbb5-439c-b5eb-7fff598480ba c2b12ec6592a4259b2e2b45b7f278150 2c398f94ad5e410bb0d8be60ddf60d84] Clear capabi
lities
2014-01-08 10:22:41.633 7705 DEBUG cinder.volume.manager [req-713496ad-cbb5-439c-b5eb-7fff598480ba c2b12ec6592a4259b2e2b45b7f278150 2c398f94ad5e410bb0d8be60ddf60d84] volume 8b97
183f-4a12-4e75-9483-3af5322de07c: removing export delete_volume /usr/lib/python2.6/site-packages/cinder/volume/manager.py:297
2014-01-08 10:22:41.634 7705 DEBUG cinder.volume.manager [req-713496ad-cbb5-439c-b5eb-7fff598480ba c2b12ec6592a4259b2e2b45b7f278150 2c398f94ad5e410bb0d8be60ddf60d84] volume 8b97
183f-4a12-4e75-9483-3af5322de07c: deleting delete_volume /usr/lib/python2.6/site-packages/cinder/volume/manager.py:299
2014-01-08 10:22:41.635 7705 DEBUG cinder.openstack.common.lockutils [req-713496ad-cbb5-439c-b5eb-7fff598480ba c2b12ec6592a4259b2e2b45b7f278150 2c398f94ad5e410bb0d8be60ddf60d84]
 Got semaphore "glusterfs" for method "delete_volume"... inner /usr/lib/python2.6/site-packages/cinder/openstack/common/lockutils.py:191
2014-01-08 10:22:41.636 7705 WARNING cinder.volume.drivers.glusterfs [req-713496ad-cbb5-439c-b5eb-7fff598480ba c2b12ec6592a4259b2e2b45b7f278150 2c398f94ad5e410bb0d8be60ddf60d84]
 Volume volume-8b97183f-4a12-4e75-9483-3af5322de07c does not have provider_location specified, skipping
2014-01-08 10:22:41.674 7705 DEBUG cinder.quota [req-713496ad-cbb5-439c-b5eb-7fff598480ba c2b12ec6592a4259b2e2b45b7f278150 2c398f94ad5e410bb0d8be60ddf60d84] Created reservations
 ['ccf49336-68c5-4621-8f4c-9a26e794fab6', '6f18c003-2679-413c-b8ca-adbe1325ef63'] reserve /usr/lib/python2.6/site-packages/cinder/quota.py:750
2014-01-08 10:22:41.679 7705 DEBUG cinder.volume.manager [req-713496ad-cbb5-439c-b5eb-7fff598480ba c2b12ec6592a4259b2e2b45b7f278150 2c398f94ad5e410bb0d8be60ddf60d84] volume 8b97183f-4a12-4e75-9483-3af5322de07c: glance metadata deleted delete_volume /usr/lib/python2.6/site-packages/cinder/volume/manager.py:336
2014-01-08 10:22:41.695 7705 INFO cinder.volume.manager [req-713496ad-cbb5-439c-b5eb-7fff598480ba c2b12ec6592a4259b2e2b45b7f278150 2c398f94ad5e410bb0d8be60ddf60d84] volume 8b97183f-4a12-4e75-9483-3af5322de07c: deleted successfully


Version-Release number of selected component (if applicable):
openstack-cinder-2014.1-0.2.b1.el6.noarch
python-cinderclient-1.0.7-1.el6.noarch
python-cinder-2014.1-0.2.b1.el6.noarch

How reproducible:
25%

Steps to Reproduce:
1. delete a volume that's in an error status

Actual results:
the volume is still in the glusterFS share but the Cinder thinks that it has deleted it.

Expected results:
the volume should be deleted from the share.

Additional info:

Comment 1 Eric Harney 2014-01-13 21:42:02 UTC

This code path causes the delete operation to skip most of the process:

Volume volume-8b97183f-4a12-4e75-9483-3af5322de07c does not have provider_location specified, skipping

Did anything break during the creation process?  Can you upload a full cinder-volume log?

No provider_location in the database indicates that Cinder does not know where the data for that volume is located.

Comment 2 Yogev Rabl 2014-03-27 08:52:59 UTC

there was no problem with the creation process & the logs are not available.