keyword arg “oldname" to utils.execute prevents cinder-volume service from starting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
New
|
Undecided
|
Unassigned |
Bug Description
I'm using OpenStack Grizzly release. I tried to delete volume when cinder-volumes service was not running. This caused volume to be in 'deleting' state forever. Restarting of cinder-volumes raises that exception:
2013-07-30 13:41:15 INFO [cinder.service] Starting 1 workers
2013-07-30 13:41:15 INFO [cinder.service] Started child 21573
2013-07-30 13:41:15 AUDIT [cinder.service] Starting cinder-volume node (version 2013.1.2)
2013-07-30 13:41:15 INFO [cinder.
2013-07-30 13:41:15 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/
old_
File "/usr/lib/
self.
File "/usr/lib/
**kwargs)
File "/usr/lib/
self.
File "/usr/lib/
'to utils.execute: %r') % kwargs)
Error: Got unknown keyword args to utils.execute: {'old_name': None}
2013-07-30 13:41:15 INFO [cinder.service] Child 21573 exited with status 2
2013-07-30 13:41:15 INFO [cinder.service] _wait_child 1
2013-07-30 13:41:15 INFO [cinder.service] wait wrap.failed True
summary: |
- Cinder volume stucked in deleting state + keyword arg “oldname" to utils.execute prevents cinder-volume service + from starting |
Hi, /bugs.launchpad .net/cinder/ +bug/1175207) for more details.
This bug has nothing to do with the volume in deleting status. It happens when cinder trying to export another volume in available status. It's a known bug which is reported and fixed after Cinder Havana-1, please refer to (https:/