ViPR used as Cinder-Volume: create volume fails

Hi,

Trying to create a cinder-volume using ViPR, I have setup my opensatck (IceHouse) with the following information:

cinder.conf

[viprblockdriver]

volume_driver = cinder.volume.drivers.emc.vipr.emc_vipr_fc.EMCViPRFCDriver

vipr_hostname=vipr-client-210.

vipr_port=4443

vipr_username=cinder@

vipr_password=xxxxxxxxx

vipr_cli_path=/opt/vipr/cli/bin

vipr_tenant=EscalaTenant

vipr_project=EscalaProject

vipr_varray=VMAX40K_VA

vipr_cookiedir=/tmp

vipr_storage_vmax=True

Then I started cinder, all is fine...

I registered a new volume type, and configure it:

# cinder type-list

| ID |         Name        |

| f71ce2ac-7d91-4484-9ff9-911cdc1b4822 |      VMAX40K_VP     |

# cinder extra-specs-list

| ID |         Name        | extra_specs |

| f71ce2ac-7d91-4484-9ff9-911cdc1b4822 |      VMAX40K_VP | {u'volume_backend_name': u'EMCViPRFCDriver', u'ViPR:VPOOL': u'VMAX40K_VP'} |

I went to the Horizon UI, and created a new volume ... but the exec fails almost instantly. Looking at the logs I found a trace in api.log, but nothing else !!

1. api.log:2014-10-06 19:59:07.796 32090 AUDIT cinder.api.v1.volumes [req-1c7e361e-c0de-4748-956d-7c48d3635c8e b04b9319699a43d08465a60e21f9b823 52b4c58cc1e74843a01b1143e7d4e09e - - -] vol={'migration_status': None, 'availability_zone': u'nova', 'terminated_at': None, 'updated_at': datetime.datetime(2014, 10, 6, 17, 51, 11), 'provider_geometry': None, 'snapshot_id': None, 'ec2_id': None, 'mountpoint': None, 'deleted_at': None, 'id': u'72a586b7-f3bd-4b7e-a679-1b1ea2262936', 'size': 3L, 'user_id': u'b04b9319699a43d08465a60e21f9b823', 'attach_time': None, 'attached_host': None, 'display_description': u'bou', 'volume_admin_metadata': [], 'encryption_key_id': None, 'project_id': u'52b4c58cc1e74843a01b1143e7d4e09e', 'launched_at': None, 'scheduled_at': None, 'status': u'error', 'volume_type_id': u'f71ce2ac-7d91-4484-9ff9-911cdc1b4822', 'deleted': False, 'provider_location': None, 'host': None, 'source_volid': None, 'provider_auth': None, 'display_name': u'bou', 'instance_uuid': None, 'bootable': False, 'created_at': datetime.datetime(2014, 10, 6, 17, 51, 10), 'attach_status': u'detached', 'volume_type': , '_name_id': None, 'volume_metadata': []}
2. # grep f71ce2ac volume.log
3. # grep bou volume.log
4. # grep VMAX volume.log

So, does someone has an idea how I can debug this further? The surprise is that it fails instantly, so I guess the error is not in ViPR itself, but I am unable to find the root cause for it.

Thanks!