Hi Guys,
I have created a Public Catalog and exported a Nexus 1000v ovf file in that catalog. Since this is Public catalog it has rights to publish this catalog to all organizations.
I have an organization named "developers". This organization is able to see the public catalog and deploy an new vApp from it. I can see on vCenter as new vApp appearing under developers resource pool. But poweron of this vApp is failing with below error message
" The operation could not be performed because the argument is invalid. A specified parameter was not correct.
spec.memoryAllocation.reservation
vCenter Server task (moref: task-1201) failed in vCenter Server 'Cloud_VC' (7b35a50a-dea1-48a2-9ae4-b38c74f8ffbb).
- A specified parameter was not correct.
spec.memoryAllocation.reservation"
I have assigned 5 GB RAM to my org vDC and I am using "Reservation Pool" allocation model. Also I have tried giving 1 GB, 2 GB and 3 GB RAM to this Nexus1k vApp at the time of deploying from catalog but every time i am getting same error.
Any help in this will be much appreciated.
Problem is with your catalogue here.
Nexus suppose to work with integrating vcloud director parallely. not to be deploy inside as a vapp.And NExus have its own requirement which interact with the dvswitch. i will suggest you to deploy some other vapp like windows/linux and see if that works.
In the deployed VM, can you go into properties and look at the two tabs:
1. There is one about the OVF details and see if there are any missing or incorrect values
2. Go into the tab about the tab about what the reservation values are for the VM and make sure those have appropriate values there as well.
Hi Jonathan,
I didnot understand your point clearly. Where exactly I should look. In my vCD or at vsphere level. If vCD then where exactly?
In vCloud Director:
1. Open up the vApp in question, go into the list of VMs for the vApp.
2. Right Click the VM, select Properties.
3. There should be several tabs here, like General ... Hardware ... etc
I think the one with the OVF properties is called "Guest Properties". This would be similar to values you had to enter if you deployed the same OVF to vCenter.
I think the reservation values is called "Resource Allocation".
I'm doing this from memory ... so don't quote me on the exact names of the tabs.
Hi John,
I tried re-configuring the vApp and set cpu and memory reservation as 0 but now I am getting different error. I have attached the screenshot of the error for your reference.
can you screen cap the Guest Properties tab as well?
IamTHEvilONE please find the attached screenshot of guest properties tab.
I tried looking for error on vcd itself by watching the log file in real time and got bunch of java codes. Only 1st line and 17th line I can understand in this and its telling same thing which I am getting in vcd console.
com.vmware.ssdc.util.LMException: Unable to start vApp "Nexus1k".
at com.vmware.ssdc.backend.AbstractVAppImpl.deploySubset(AbstractVAppImpl.java:526)
at com.vmware.ssdc.backend.services.impl.VAppDeploymentManagerImpl.deployVm(VAppDeploymentManagerImpl.java:398)
at com.vmware.vcloud.vapp.impl.VAppServiceImpl.deployTask(VAppServiceImpl.java:1894)
at com.vmware.vcloud.vapp.impl.VAppServiceImpl.executeTask(VAppServiceImpl.java:691)
at com.vmware.vcloud.backendbase.management.system.TaskActivity$ExecutePhase$2.doInSecurityContext(TaskActivity.java:427)
at com.vmware.vcloud.backendbase.management.system.TaskActivity$ExecutePhase$2.doInSecurityContext(TaskActivity.java:421)
at com.vmware.vcloud.backendbase.management.system.TaskActivity$SecurityContextTemplate.executeForOrgAndUser(TaskActivity.java:674)
at com.vmware.vcloud.backendbase.management.system.TaskActivity$ExecutePhase.execute(TaskActivity.java:421)
at com.vmware.vcloud.backendbase.management.system.TaskActivity$ExecutePhase.invoke(TaskActivity.java:354)
at com.vmware.vcloud.activity.executors.ActivityRunner.run(ActivityRunner.java:109)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.vmware.ssdc.util.LMException: Invalid vApp properties: Property value not defined in value map.,Property value not defined in value map..
at com.vmware.ssdc.backend.AbstractVAppImpl.customizeVMs(AbstractVAppImpl.java:1007)
at com.vmware.ssdc.backend.AbstractVAppImpl.deploy(AbstractVAppImpl.java:592)
at com.vmware.ssdc.backend.AbstractVAppImpl.access$000(AbstractVAppImpl.java:105)
at com.vmware.ssdc.backend.AbstractVAppImpl$1.run(AbstractVAppImpl.java:489)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at com.vmware.ssdc.backend.AbstractVAppImpl.deploySubset(AbstractVAppImpl.java:504)
Okay. This I might be able to work with ... I wouldn't expect anyone outside VMware to know what most/any of this means.
In seeing the "Guest Properties" there is one item missing. I think the Nexus 1000v has a few deployment modes, like "Installer" vs "Manually Configure" which is selected as a drop down box. vCloud Director won't be able to handle this as far as I know.
If the Nexus OVF descriptor uses a "ValueMap" (list of string values), I'm not sure if this will work. We might pick the default, but sometimes the default is not a valid selection.
e.g. first value might be "pick one of the below", 2nd would be "installer", 3rd "manual config". the first does nothing, but the other 2 do.
Problem is with your catalogue here.
Nexus suppose to work with integrating vcloud director parallely. not to be deploy inside as a vapp.And NExus have its own requirement which interact with the dvswitch. i will suggest you to deploy some other vapp like windows/linux and see if that works.
Hi John,
I guess you are right here. I discussed this with my fellow counterpart Anjani_Kumar last night and we tried deploying a server 2003 vm from catalog and it was deployed without any issues.