Volume creation error for 3PAR and LHN using Volume TYPE

Asked by Vivekanandan B

We are facing an issue in creating volume of particular volume type(3par or LHN) when using multi-backend drivers in cinder.conf file.
Creating a volume of type “lvm” is only successful as it’s the default driver.

On creating a volume of type LHN or 3par, we are getting the following error in the “cinder-scheduler.log”
2013-04-26 06:47:01 ERROR [cinder.scheduler.manager] Failed to schedule_create_volume: No valid host was found.

Please let us know if you ever faced such issues during your testing

However creating a volume with only one driver is sucessfull.

Question information

Language:
English Edit question
Status:
Solved
For:
Cinder Edit question
Assignee:
No assignee Edit question
Solved by:
Shanthakumar K
Solved:
Last query:
Last reply:
Revision history for this message
Shanthakumar K (shantha-kumar) said :
#1

can you share the cinder conf file ?

Revision history for this message
Vivekanandan B (bvivek) said :
#2

root@grzrc3:/home/iaasc# cat /etc/cinder/cinder.conf
[DEFAULT]
rootwrap_config=/etc/cinder/rootwrap.conf
sql_connection = mysql://cinderUser:cinderPass@10.1.0.29/cinder
api_paste_confg = /etc/cinder/api-paste.ini
iscsi_helper=tgtadm
volume_name_template = volume-%s
volume_group = cinder-volumes
volumes_dir = /etc/cinder/volumes
state_path = /var/lib/cinder
lock_path = /var/lock/cinder
verbose = True
auth_strategy = keystone
debug=true
#osapi_volume_listen_port=5900

# a list of backends that will be served by this compute node
enabled_backends=driver-1,driver-2,driver-3

###################################################################################
#LVM Required Settings
###################################################################################
[driver-1]
iscsi_helper=tgtadm
volume_group = cinder-volumes
volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver
volume_backend_name=LVM_iSCSI

###################################################################################
#LHN Required Settings
###################################################################################
[driver-2]
volume_driver=cinder.volume.drivers.san.hp_lefthand.HpSanISCSIDriver
volume_backend_name=LHN_iSCSI
volume_group = cinder-volumes
iscsi_helper=tgtadm
san_ip=10.1.0.153
san_login=vivek
san_password=<pwd>
san_ssh_port=16022
san_clustername=Cloud_LHN
san_thin_provision=True
san_is_local=False

###################################################################################
#3PAR Required Settings
###################################################################################
[driver-3]
volume_driver=cinder.volume.drivers.san.hp.hp_3par_fc.HP3PARFCDriver
volume_backend_name=PAR_FC

# 3PAR WS API Server URL
hp3par_api_url=https://15.218.123.105:8080/api/v1

# 3PAR Super user username
hp3par_username=admin

# 3PAR Super user password
hp3par_password=sunflower

# 3PAR domain to use
hp3par_domain=CloudOS-Domain

# 3PAR CPG to use for volume creation
hp3par_cpg=Vivek-RAID6-8

# IP address of SAN controller for SSH access to the array
san_ip=15.218.123.105

# Username for SAN controller for SSH access to the array
san_login=3paradm

# Password for SAN controller for SSH access to the array
san_password=<pwd>

# FIBRE CHANNEL(uncomment the next line to enable the FC driver)
#volume_driver=cinder.volume.drivers.san.hp.hp_3par_fc.HP3PARFCDriver

# iSCSI (uncomment the next line to enable the iSCSI driver and the iscsi_ip_address)
# volume_driver=cinder.volume.drivers.san.hp.hp_3par_iscsi.HP3PARISCSIDriver

# The port that the iSCSI daemon is listening on
#iscsi_ip_address="10.10.220.253"

## OPTIONAL SETTING
# Enable HTTP debugging to 3PAR
hp3par_debug=true

# The CPG to use for Snapshots for volumes. If empty hp3par_cpg will be used.
hp3par_snap_cpg=Vivek-RAID6-8

# Time in hours to retain a snapshot. You can't delete it before this expires.
hp3par_snapshot_retention=48

# Time in hours when a snapshot expires and is deleted. This must be larger than retention.
hp3par_snapshot_expiration=72

Revision history for this message
Best Shanthakumar K (shantha-kumar) said :
#3

Its a problem with volume_backend_name for each storage, use the backend specified in scheduler log!!!!!

This will resolve the problem.

Backend name has been hardcoded!!!!

Revision history for this message
Vivekanandan B (bvivek) said :
#4

Thank You Shanthakumar, it solved my problem.

Revision history for this message
Vivekanandan B (bvivek) said :
#5

Thanks shausy, that solved my question.