volume is not deleted in cinder db
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Low
|
Adalberto Medeiros | ||
Grizzly |
Fix Released
|
Low
|
Adalberto Medeiros |
Bug Description
I have the IBM v7000 Storwize storage connected to the controller server and cinder configured to manage it.
I'm running openstack grizzly, on Fedora 19, installed by packstack.
I added one volume, it successfully created the volume on the san storage.
When i tried to delete it, it deletes the volume from the storage but not from cinder database (keeps it in "deleting" state).
The failure and debug info (from cinder/volume.log)
2013-08-07 14:39:32 DEBUG [cinder.
2013-08-07 14:39:32 DEBUG [cinder.
2013-08-07 14:39:32 DEBUG [cinder.
2013-08-07 14:39:32 DEBUG [cinder.utils] backend <module 'cinder.
2013-08-07 14:39:32 DEBUG [cinder.
2013-08-07 14:39:32 INFO [cinder.
2013-08-07 14:39:32 DEBUG [cinder.
2013-08-07 14:39:32 INFO [cinder.
2013-08-07 14:39:32 INFO [cinder.
2013-08-07 14:39:32 INFO [cinder.
2013-08-07 14:39:32 DEBUG [cinder.
2013-08-07 14:39:32 DEBUG [cinder.
2013-08-07 14:39:32 DEBUG [cinder.
2013-08-07 14:39:32 DEBUG [cinder.
2013-08-07 14:39:32 DEBUG [cinder.
2013-08-07 14:39:32 DEBUG [cinder.utils] Running cmd (SSH): lsvdisk -bytes -delim ! volume-
2013-08-07 14:39:32 DEBUG [cinder.utils] Result was 1
2013-08-07 14:39:32 ERROR [cinder.
Command: lsvdisk -bytes -delim ! volume-
Exit code: 1
Stdout: ''
Stderr: 'CMMVC5754E The specified object does not exist, or the name supplied does not meet the naming rules.\n'
2013-08-07 14:39:33 ERROR [cinder.
2013-08-07 14:39:33 ERROR [cinder.
command: lsvdisk -bytes -delim ! volume-
stdout:
stderr: CMMVC5754E The specified object does not exist, or the name supplied does not meet the naming rules.
2013-08-07 14:39:33 DEBUG [cinder.
2013-08-07 14:39:33 INFO [cinder.
2013-08-07 14:39:33 DEBUG [cinder.quota] Created reservations ['279b2eaf-
2013-08-07 14:39:33 ERROR [cinder.service] Unhandled exception
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
launcher.
File "/usr/lib/
server.start()
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
return IMPL.volume_
File "/usr/lib/
return f(*args, **kwargs)
File "/usr/lib/
'updated_at': literal_
File "/usr/lib64/
update_
File "/usr/lib64/
self.
File "/usr/lib64/
"Could not evaluate current criteria in Python. "
InvalidRequestE
relevant cinder.conf info:
storwize_
#storwize_
storwize_
storwize_
storwize_
storwize_
storwize_
storwize_
san_ip=9.114.219.37
san_login=****
san_password=****
san_clustername
san_is_local=false
volume_
tags: | added: grizzly-backport-potential |
Changed in cinder: | |
milestone: | none → havana-3 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | havana-3 → 2013.2 |
Changed in cinder: | |
importance: | Undecided → Low |
tags: | removed: grizzly-backport-potential in-stable-grizzly |
Hi Adalberto, b221d0c6- c1dd-488a- a80d-ffb27163ad f8 volume_ glance_ metadata_ delete_ by_volume. I will look into this.
There seem to be two issues here:
1. The driver cannot find the volume. Is it in fact there? What is the output of:
lsvdisk -bytes -delim ! volume-
2. There is an issue not related to the driver when Cinder calls self.db.