Unable to start vApp-Invalid vApp properties:Invalid property value size


I recently deployed vSphere replication appliance in vCloud Director and while powering it on I was facing one error

Unable to start vAPP- Invalid vApp properties:Invalid property value size

Due to this power on operation on vApp was failing time and again.

I checked the vCD logs and did not found any error messages for my vApp. All I got was few debug messages:


<em>2016-05-29 09:56:25,597 | INFO | nf-activity-pool-272 | VC20VirtualServer | Created device change list for [name = vrs01 (3fd990d6-6ee2-4618-8446-9067f8ecdd02), valref = [vcId=03dc414f-6385-43e5-b95f-1d7ca8db3aa8, moref=vm-5205]] for synchronizing nics. | requestId=cf0ea3dc-8541-4d5a-b37b-fad3b3cde71b,request=POST https://x.x.x.x/cloud/amf,requestTime=1464515782276,remoteAddress=172.20.1.2:58308,userAgent=Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML...,accept=*/* method=vAppService.updateVAppVmWithStorageClass vcd=1d114aae-e514-4fc6-a30d-8d5fc7c8c286,task=1fb5f553-e269-4a76-8632-ccf9bb1c5b9d activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:1fb5f553-e269-4a76-8632-ccf9bb1c5b9d) activity=(com.vmware.vcloud.fabric.net.activities.ConstituteNetworkedVmActivity,urn:uuid:56dc4e55-a460-4ac9-9dab-7eb5f76e5248)</em>

<em>2016-05-29 09:56:25,599 | INFO | nf-activity-pool-272 | VC20VirtualServer | Invoking reconfigure vm [name = vrs01 (3fd990d6-6ee2-4618-8446-9067f8ecdd02), valref = [vcId=03dc414f-6385-43e5-b95f-1d7ca8db3aa8, moref=vm-5205], changeVersion 2016-05-29T09:52:33.186794Z] for synchronizing nics. | requestId=cf0ea3dc-8541-4d5a-b37b-fad3b3cde71b,request=POST https://x.x.x.x/cloud/amf,requestTime=1464515782276,remoteAddress=172.20.1.2:58308,userAgent=Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML...,accept=*/* method=vAppService.updateVAppVmWithStorageClass vcd=1d114aae-e514-4fc6-a30d-8d5fc7c8c286,task=1fb5f553-e269-4a76-8632-ccf9bb1c5b9d activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:1fb5f553-e269-4a76-8632-ccf9bb1c5b9d) activity=(com.vmware.vcloud.fabric.net.activities.ConstituteNetworkedVmActivity,urn:uuid:56dc4e55-a460-4ac9-9dab-7eb5f76e5248)</em>

<em>2016-05-29 09:56:26,617 | DEBUG | val-activity-pool-273 | TaskManager | result null (or not a moref type) for task [moref=task-55625, state=SUCCESS, taskName=ReconfigVM_Task, progress=null, entityName=vrs01 (3fd990d6-6ee2-4618-8446-9067f8ecdd02)] when waiting for inventory update | requestId=cf0ea3dc-8541-4d5a-b37b-fad3b3cde71b,request=POST https://x.x.x.x/cloud/amf,requestTime=1464515782276,remoteAddress=172.20.1.2:58308,userAgent=Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML...,accept=*/* method=vAppService.updateVAppVmWithStorageClass vcd=1d114aae-e514-4fc6-a30d-8d5fc7c8c286,task=1fb5f553-e269-4a76-8632-ccf9bb1c5b9d activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:1fb5f553-e269-4a76-8632-ccf9bb1c5b9d) activity=(com.vmware.vcloud.fabric.net.activities.ConstituteNetworkedVmActivity,urn:uuid:56dc4e55-a460-4ac9-9dab-7eb5f76e5248) activity=(com.vmware.vcloud.val.internal.impl.ReconfigureVmActivity,urn:uuid:0b07e9fd-fb2c-4926-95d1-22f063ca77db)</em>

<em>2016-05-29 09:56:27,163 | DEBUG | backend-activity-pool-46 | JobString | Job object - Object : vrs01(com.vmware.vcloud.entity.vm:3fd990d6-6ee2-4618-8446-9067f8ecdd02) operation name: VAPP_UPDATE_VM | requestId=cf0ea3dc-8541-4d5a-b37b-fad3b3cde71b,request=POST https://x.x.x.x/cloud/amf,requestTime=1464515782276,remoteAddress=172.20.1.2:58308,userAgent=Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML...,accept=*/* method=vAppService.updateVAppVmWithStorageClass vcd=1d114aae-e514-4fc6-a30d-8d5fc7c8c286,task=1fb5f553-e269-4a76-8632-ccf9bb1c5b9d activity=(com.vmware.vcloud.backendbase.management.system.TaskActivity,urn:uuid:1fb5f553-e269-4a76-8632-ccf9bb1c5b9d)</em>

This issue generally occurs when you are deploying pre-built ovf templates like vCAC appliance or vSphere Replication appliance or appliance from any other vendors in vCD. The reason of this error is there are some configurable parameters associated with vApps which needs a value before you attempt to power-on a VM. These parameters can be found on guest os properties as shown below:

vapp

In my case password field was left blank which was preventing the vApp from getting powered on. Once I supplied the password, the vApp booted up without any further issues.

If you have vCD in your environment or if you are running your VM’s in vCloud Air and face the same issue, try following steps:

Check the properties of each VM in the vApp. When appliances are deployed in vCloud Director you will need to fill in the guest properties prior to starting the vApp/VM. If required properties are missing in order to configure the VM, the start up process will fail due to null values.

  1. Right-click the VM and click Properties.
  2. Click the “Guest Properties” tab.
  3. Enter the property requirements for each appliance and click OK.

Once you complete the steps that are highlighted in red for each appliance the vApp should start.

I hope you enjoyed reading this post. Feel free to share this on social media if it is worth sharing. Be sociable:)

About Alex Hunt

Hi All I am Manish Kumar Jha aka Alex Hunt. I am currently working in VMware Software India Pvt Ltd as Operations System Engineer (vCloud Air Operations). I have around 5 Years of IT experience and have exposure on VMware vSphere, vCloud Director, RHEL and modern data center technologies like Cisco UCS and Cisco Nexus 1000v and NSX. If you find any post informational to you please press like and share it across social media and leave your comments if you want to discuss further on any post. Disclaimer: All the information on this website is published in good faith and for general information purpose only. I don’t make any warranties about the completeness, reliability and accuracy of this information. Any action you take upon the information you find on this blog is strictly at your own risk. The Views and opinions published on this blog are my own and not the opinions of my employer or any of the vendors of the product discussed.
This entry was posted in vCloud Director, Vmware. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s