[
https://issues.apache.org/jira/browse/CLOUDSTACK-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Purushothama reopened CLOUDSTACK-2124:
----------------------------------------------
Was any changes made to the code to fix the Deployment Planner behavior that
you mentioned in your comment. Reopening to the bug in order to get the
corresponding commit information to test the fix.
> VM Deployment Failure on VMWare ESXi Host: StartCommand failed due to
> java.lang.RuntimeException
> ------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2124
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2124
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: Chandan Purushothama
> Assignee: Sateesh Chodapuneedi
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: logsandmysqldumps.zip
>
>
> I was able to deploy a VM using the default CentOS Template on the Setup. I
> registered a new Template (OS: Windows XP SP3) later and tried to deploy a VM
> from it. I see that the VM deployment failed job failed due to Runtime
> Exception that says " The available Memory resources in the parent resource
> pool are insufficient for the operation."
> I will attach the mysqldump of the cloud database and the management server
> logs to the bug report.
> ====================================
> Exception Seen on the Management Server Logs:
> ====================================
> 2013-04-20 14:59:32,342 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-279:10.223.59.66) Prepare NIC at new device
> {"operation":"ADD","device":{"addressType":"Manual","macAddress":"02:00:64:0b:00:03","key":-3,"backing":{"network":{"value":"network-26276","type":"Network"},"deviceName":"cloud.guest.2586.200.1-vSwitch0"},"connectable":{"startConnected":true,"allowGuestControl":true,"connected":true},"unitNumber":2}}
> 2013-04-20 14:59:32,342 DEBUG [vmware.mo.HostMO]
> (DirectAgent-279:10.223.59.66) find VM i-3-5-SYSVMTMPL on host
> 2013-04-20 14:59:32,342 DEBUG [vmware.mo.HostMO]
> (DirectAgent-279:10.223.59.66) VM i-3-5-SYSVMTMPL found in host cache
> 2013-04-20 14:59:32,360 INFO [vmware.resource.VmwareResource]
> (DirectAgent-279:10.223.59.66) Configure VNC port for VM i-3-5-SYSVMTMPL,
> port: 5943, host: 10.223.59.66
> 2013-04-20 14:59:32,890 DEBUG [agent.manager.AgentManagerImpl]
> (AgentManager-Handler-5:null) Ping from 3
> 2013-04-20 14:59:32,988 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 1 routers to update status.
> 2013-04-20 14:59:32,989 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-04-20 14:59:33,238 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 1 routers to update status.
> 2013-04-20 14:59:33,240 DEBUG
> [network.router.VirtualNetworkApplianceManagerImpl]
> (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-04-20 14:59:34,348 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-114:null) Ignoring vm i-3-5-SYSVMTMPL because of a lag in
> starting the vm.
> 2013-04-20 14:59:34,355 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-114:null) VM 668fb8f8435034e2abdbcb82f31becb8 is now missing
> from host report but we detected that it might be migrated to other host by
> vCenter
> 2013-04-20 14:59:34,355 DEBUG [vmware.resource.VmwareResource]
> (DirectAgent-114:null) VM 668fb8f8435034e2abdbcb82f31becb8 is now missing
> from host report and VM is not at starting/migrating state, remove it from
> host VM-sync map, oldState: Stopped
> 2013-04-20 14:59:34,363 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-114:null) Ping from 1
> 2013-04-20 14:59:38,848 WARN [vmware.resource.VmwareResource]
> (DirectAgent-279:10.223.59.66) StartCommand failed due to Exception:
> java.lang.RuntimeException
> Message: The available Memory resources in the parent resource pool are
> insufficient for the operation.
> java.lang.RuntimeException: The available Memory resources in the parent
> resource pool are insufficient for the operation.
> at
> com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:291)
> at
> com.cloud.hypervisor.vmware.mo.VirtualMachineMO.powerOn(VirtualMachineMO.java:184)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2370)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:433)
> at
> com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:679)
> 2013-04-20 14:59:38,853 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-279:null) Seq 1-1166872010: Response Received:
> 2013-04-20 14:59:38,853 DEBUG [agent.transport.Request]
> (DirectAgent-279:null) Seq 1-1166872010: Processing: { Ans: , MgmtId:
> 7200344900649, via: 1, Ver: v1, Flags: 110,
> [{"StartAnswer":{"vm":{"id":5,"name":"i-3-5-SYSVMTMPL","bootloader":"HVM","type":"User","cpus":1,"minSpeed":1000,"maxSpeed":1000,"minRam":1073741824,"maxRam":1073741824,"arch":"x86_64","os":"Windows
> XP SP3
> (32-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"vncPassword":"72124c859db94896","params":{"rootDiskController":"ide","nicAdapter":"E1000","nestedVirtualizationFlag":"false"},"uuid":"16d82ef6-ff4b-4495-addd-5c42dafa4fbc","disks":[{"id":6,"name":"ROOT-5","mountPoint":"/export/home/chandan/asfmas-131-170/primary2","path":"ROOT-5-6","size":171798691840,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"2dd16067-d7b5-366d-bce7-87962a7cfe70","deviceId":0},{"id":5,"name":"DownloadedTemplate-1","size":0,"type":"ISO","storagePoolType":"ISO","deviceId":3}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"17d9fae4-608b-4120-b0d5-e3cce5596128","ip":"10.1.1.124","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:64:0b:00:03","dns1":"8.8.8.8","dns2":"8.8.4.4","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://2586","isolationUri":"vlan://2586","isSecurityGroupEnabled":false}]},"result":false,"details":"StartCommand
> failed due to Exception: java.lang.RuntimeException\nMessage: The available
> Memory resources in the parent resource pool are insufficient for the
> operation.\n","wait":0}}] }
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
