Deploying multiple vm´s from blueprint fails

[dmuligan]

Hi,

we are facing the following problem.

Deploying 3 vm´s from a single blueprint is always deploying two vm´s and the third one fails,if we deploy one by one it works fine.This is the error in the request status:

"Request failed after creating test182 and test184. Errors: Machine test183: CloneVM : The object has already been deleted or has not been completely created."

As you can see in the request status,test183 has failed due to vm has been deleted,182 and 184 are successfully deployed.

Any ideas,logs to look into,.. ?

Thank you.

[muxx]

Can you login as administrator and check Infrastructure > Monitoring > Log & Workflow history & Audit Log for any errors?

Do you use VCO/VRO workflows during provisioning? If yes, login to VCO/VRO client and verify that all your scripts finished without errors.

[GParker72]

Hi Muxx,

I'm seeing the same issue, if anyone requests more than 2 machines then the 3rd or more will fail.  

There is an error under Infrastructure > Monitoring > Log ... it's Source is"VRM Agent" and the message is "Error processing [CustomizeVM], error details: [PowerOnVM_Task] - Failed to extend swap file from 0 KB to 4194304 KB."

There are no failed events in the Infrastructure > Monitoring > Workflow History

Thanks

Graham

[muxx]

I have never seen such error, but google suggests that this could be problem with underlying storage:

Could not power on VM : msg.vmk.status.VMK_NO_RESOURCES. - Failed to extend swap file from 32768 KB...

Is this problem related to all blueprints? Try to deploy from another blueprint to make sure it is not blueprint related.

Can you try to deploy to other datastore or datastore cluster? (If you have more than one)

Are all clones deployed to same host/datastore? Let's see if it is related to specific host/datastore.

What if you login to vSphere client and check Tasks and Events for more detailed information?