volume status is in error state with HP VSA

[venkat bokka]

i have configured cinder with HP VSA
when i try to create volume,Creating volume stuck with "error" status.

this is my cinder.cinf

rabbit_host = 172.16.128.38
rabbit_userid = guest
rabbit_password = guest
rabbit_virtual_host=/
api_paste_config = /etc/cinder/api-paste.ini
rootwrap_config=/etc/cinder/rootwrap.conf
auth_strategy=keystone
verbose= True
iscsi_ip_address=172.16.128.38
iscsi_helper=tgtadm
volumes_dir=/var/lib/cinder/volumes
volume_group=cinder-volumes

[database]
sql_connection = mysql://cinderUser:cinderPass@172.16.128.38/cinder

hplefthand_api_url=https://172.16.128.37:8081/lhos
hplefthand_username=admin
hplefthand_password=admin123
hplefthand_clustername=cluster1
volume_driver=cinder.volume.drivers.san.hp.hp_lefthand_iscsi.HPLeftHandISCSIDriver
volume_backend_name=vsa01
hplefthand_iscsi_chap_enabled=false
hplefthand_debug=false

these are log files

cinder-schduler.log

2014-07-09 04:06:33.574 3789 INFO cinder.openstack.common.service [-] Caught SIGTERM, exiting
2014-07-09 04:06:34.265 8367 AUDIT cinder.service [-] Starting cinder-scheduler node (version 2014.1.1)
2014-07-09 04:06:34.282 8367 INFO oslo.messaging._drivers.impl_rabbit [req-3c5bfb48-6fb3-4cf9-9bd1-b6aaf9d19b22 - - - - -] Connected to AMQP server on 172.16.128.38:5672
2014-07-09 04:06:34.667 8367 INFO oslo.messaging._drivers.impl_rabbit [-] Connected to AMQP server on 172.16.128.38:5672
2014-07-09 04:07:58.593 8367 WARNING cinder.context [-] Arguments dropped when creating context: {'user': u'34047c17bb17419e8d9df51186245c24', 'tenant': u'194dc872b59547c0ae62bdf474eb12c4', 'user_identity': u'34047c17bb17419e8d9df51186245c24 194dc872b59547c0ae62bdf474eb12c4 - - -'}
2014-07-09 04:07:58.960 8367 WARNING cinder.scheduler.host_manager [req-39f05f81-128c-41df-a8ec-527478ecbe3a 34047c17bb17419e8d9df51186245c24 194dc872b59547c0ae62bdf474eb12c4 - - -] volume service is down or disabled. (host: hLinux)
2014-07-09 04:07:58.962 8367 ERROR cinder.scheduler.flows.create_volume [req-39f05f81-128c-41df-a8ec-527478ecbe3a 34047c17bb17419e8d9df51186245c24 194dc872b59547c0ae62bdf474eb12c4 - - -] Failed to schedule_create_volume: No valid host was found.

cinder-volume.log

2014-07-09 04:06:33.754 3825 INFO cinder.openstack.common.service [-] Caught SIGTERM, stopping children
2014-07-09 04:06:33.755 4021 INFO cinder.openstack.common.service [-] Caught SIGTERM, exiting
2014-07-09 04:06:33.758 3825 INFO cinder.openstack.common.service [-] Waiting on 1 children to exit
2014-07-09 04:06:33.764 3825 INFO cinder.openstack.common.service [-] Child 4021 exited with status 1
2014-07-09 04:06:34.418 8402 INFO cinder.openstack.common.service [-] Starting 1 workers
2014-07-09 04:06:34.420 8402 INFO cinder.openstack.common.service [-] Started child 8430
2014-07-09 04:06:34.426 8430 AUDIT cinder.service [-] Starting cinder-volume node (version 2014.1.1)
2014-07-09 04:06:34.428 8430 INFO cinder.volume.manager [req-c16fa19f-a42c-42f2-b67a-6e956f29b9f8 - - - - -] Starting volume driver HPLeftHandISCSIDriver (1.0.2)

cinder-manage service list output

Binary Host Zone Status State Updated At
cinder-scheduler hLinux nova enabled :-) 2014-07-09 10:20:23.546227
cinder-volume hLinux nova enabled XXX 2014-07-09 10:06:27.110781

thanks for any help.

[Sunitha K (sunitha-kannan)]

I too came across this problem.

[venkat bokka (naga-venkata-durga-rao-b)]

i am not seeing it now

[Walt Boring (walter-boring)]

The scheduler log says it all here. The scheduler couldn't find a valid host. You need to make sure the driver is up and initialized, and if you are using a volume type, one that points to a working driver.

Please provide the c-vol (cinder volume) log and prove that the driver successful initialized.

[Sean McGinnis (sean-mcginnis)]

Automatically unassigning due to inactivity.