Deploy heat stack with 4 or more cinder volumes to VMware failed
Using IBM Cloud Orchestrator Admin UI (Horizon) to deploy heat stack with 4 or more cinder volumes to VMware vCenter v5.5 U2 failed.
The status on UI is:
Create Failed: CREATE aborted
The VMware vCenter task shows error:
Status: Invalid configuration for device '0'.
Accepted answer
Cause: There are occasions that the VM database and the VMX are out of synch due to multiple operations on vCenter at the same time.
Resolution: To add dependency on volume attachment steps so they will be executed one by one.
See below example.
Change the volume definition part in heat stack from:
steven-stack-test_u1:
properties: {size: 1}
type: OS::Cinder::Volume
steven-stack-test_u1_attachment:
properties:
instance_uuid: {get_resource: steven-stack-test}
volume_id: {get_resource: steven-stack-test_u1}
type: OS::Cinder::VolumeAttachment
steven-stack-test_u2:
properties: {size: 1}
type: OS::Cinder::Volume
steven-stack-test_u2_attachment:
properties:
instance_uuid: {get_resource: steven-stack-test}
volume_id: {get_resource: steven-stack-test_u2}
type: OS::Cinder::VolumeAttachment
steven-stack-test_u3:
properties: {size: 1}
type: OS::Cinder::Volume
steven-stack-test_u3_attachment:
properties:
instance_uuid: {get_resource: steven-stack-test}
volume_id: {get_resource: steven-stack-test_u3}
type: OS::Cinder::VolumeAttachment
To:
steven-stack-test_u1:
properties: {size: 1}
type: OS::Cinder::Volume
steven-stack-test_u1_attachment:
properties:
instance_uuid: {get_resource: steven-stack-test}
volume_id: {get_resource: steven-stack-test_u1}
type: OS::Cinder::VolumeAttachment
steven-stack-test_u2:
properties: {size: 1}
type: OS::Cinder::Volume
steven-stack-test_u2_attachment:
properties:
instance_uuid: {get_resource: steven-stack-test}
volume_id: {get_resource: steven-stack-test_u2}
type: OS::Cinder::VolumeAttachment
depends_on: steven-stack-test_u1_attachment
steven-stack-test_u3:
properties: {size: 1}
type: OS::Cinder::Volume
steven-stack-test_u3_attachment:
properties:
instance_uuid: {get_resource: steven-stack-test}
volume_id: {get_resource: steven-stack-test_u3}
type: OS::Cinder::VolumeAttachment
depends_on: steven-stack-test_u2_attachment
Does this issue continue to be seen in vCenter v6.5 ?