Cinder-Volume fails to start after reboot

Asked by Paul Millar

This issue seems to be similar in nature to: https://answers.launchpad.net/cinder/+question/230747 however this indicates that it was a bug in Folsom that was fixed. I'm running Grizzly and still running into the same issue...

Steps:
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: https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst
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/service.py", line 227, in _start_child
    self._child_process(wrap.server)
  File "/usr/lib/python2.7/dist-packages/cinder/service.py", line 204, in _child_process
    launcher.run_server(server)
  File "/usr/lib/python2.7/dist-packages/cinder/service.py", line 95, in run_server
    server.start()
  File "/usr/lib/python2.7/dist-packages/cinder/service.py", line 355, in start
    self.manager.init_host()
  File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 149, in init_host
    self.driver.ensure_export(ctxt, volume)
  File "/usr/lib/python2.7/dist-packages/cinder/volume/drivers/lvm.py", line 391, in ensure_export
    old_name=old_name)
  File "/usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py", line 225, in create_iscsi_target
    self._new_target(name, tid, **kwargs)
  File "/usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py", line 284, in _new_target
    **kwargs)
  File "/usr/lib/python2.7/dist-packages/cinder/volume/iscsi.py", line 73, in _run
    self._execute(self._cmd, *args, run_as_root=True, **kwargs)
  File "/usr/lib/python2.7/dist-packages/cinder/utils.py", 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@10.10.10.3/
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 = /var/lib/cinder/volumes
iscsi_ip_address=10.10.10.3
rabbit_password=secret

Question information

Language:
English Edit question
Status:
Needs information
For:
Cinder Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Vivekanandan B (bvivek) said :
#1

Hi,

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

Can you help with this problem?

Provide an answer of your own, or ask Paul Millar for more information if necessary.

To post a message you must log in.