Ask Your Question

Cinder-Volume fails to start after reboot

asked 2013-08-14 10:42:03 -0500

pqul gravatar image

This issue seems to be similar in nature to: ( however this indicates that it was a bug in Folsom that was fixed. I'm running Grizzly and still running into the same issue...

1) Installed Cinder on a node, used secondary disk formatted as LVM for the cinder-volumes and had everything working well & correctly. Used this as a base: ( 2) Rebooted machine (the host was rebooted). 3) Upon reboot, cinder volumes won't create. (As cinder-volumes fails shuts down upon start).

Cinder-Volume log message:

2013-08-14 10:23:34 INFO [cinder.service] Starting 1 workers 2013-08-14 10:23:34 INFO [cinder.service] Started child 4176 2013-08-14 10:23:34 AUDIT [cinder.service] Starting cinder-volume node (version 2013.1.2) 2013-08-14 10:23:34 ERROR [cinder.service] Unhandled exception Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/cinder/", line 227, in _start_child self._child_process(wrap.server) File "/usr/lib/python2.7/dist-packages/cinder/", line 204, in _child_process launcher.run_server(server) File "/usr/lib/python2.7/dist-packages/cinder/", line 95, in run_server server.start() File "/usr/lib/python2.7/dist-packages/cinder/", line 355, in start self.manager.init_host() File "/usr/lib/python2.7/dist-packages/cinder/volume/", line 149, in init_host self.driver.ensure_export(ctxt, volume) File "/usr/lib/python2.7/dist-packages/cinder/volume/drivers/", line 391, in ensure_export old_name=old_name) File "/usr/lib/python2.7/dist-packages/cinder/volume/", line 225, in create_iscsi_target self._new_target(name, tid, *kwargs) File "/usr/lib/python2.7/dist-packages/cinder/volume/", line 284, in _new_target *kwargs) File "/usr/lib/python2.7/dist-packages/cinder/volume/", line 73, in _run self._execute(self._cmd, args, run_as_root=True, *kwargs) File "/usr/lib/python2.7/dist-packages/cinder/", line 145, in execute 'to utils.execute: %r') % kwargs) Error: Got unknown keyword args to utils.execute: {'old_name': None} 2013-08-14 10:23:34 INFO [cinder.service] Child 4176 exited with status 2 2013-08-14 10:23:34 INFO [cinder.service] _wait_child 1 2013-08-14 10:23:34 INFO [cinder.service] wait wrap.failed True

VGDisplay Output: (showing volume is there)

root@horizon:/home/ultima# vgdisplay --- Volume group --- VG Name cinder-volumes System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 3 VG Access read/write VG Status resizable MAX LV 0 Cur LV 2 Open LV 2 Max PV 0 Cur PV 1 Act PV 1 VG Size 300.00 GiB PE Size 4.00 MiB Total PE 76799 Alloc PE / Size 13312 / 52.00 GiB Free PE / Size 63487 / 248.00 GiB VG UUID bee2WO-b7iL-8kkl-Vciq-rkJI-YT9a-0B70Cs

Cinder.conf File:

[DEFAULT] rootwrap_config = /etc/cinder/rootwrap.conf sql_connection = postgresql://cinder:secret@ api_paste_confg = /etc/cinder/api-paste.ini iscsi_helper = ietadm volume_name_template = volume-%s volume_group = cinder-volumes verbose = True auth_strategy = keystone state_path = /var/lib/cinder lock_path = /var/lock/cinder volumes_dir ... (more)

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2013-08-26 06:25:01 -0500

bvivek gravatar image


Can you check if the "iscsi" related services are running?

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2013-08-14 10:42:03 -0500

Seen: 556 times

Last updated: Aug 26 '13