You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sudha Ponnaganti (JIRA)" <ji...@apache.org> on 2013/09/01 02:19:51 UTC

[jira] [Updated] (CLOUDSTACK-4585) [VMWare] [Upgrade] Failed to start instance after reverting the VM snapshot on a Private Zone which was created prior to upgrade

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sudha Ponnaganti updated CLOUDSTACK-4585:
-----------------------------------------

    Summary: [VMWare] [Upgrade] Failed to start instance after reverting the VM snapshot on a Private Zone which was created prior to upgrade   (was: [VMWare] [Upgrade]  )
    
> [VMWare] [Upgrade] Failed to start instance after reverting the VM snapshot on a Private Zone which was created prior to upgrade 
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4585
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4585
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Snapshot
>    Affects Versions: 4.2.1
>            Reporter: Sudha Ponnaganti
>            Assignee: Kelven Yang
>            Priority: Blocker
>             Fix For: 4.2.1
>
>
> I have an upgraded setup from 307 Patch B to 4.2 .  I have one VMWARE private zone before upgrade.
>  
> After upgrade I  created VM snapshot for one of the instance In this zone.   Later  reverted to this VM snapshot.  Now VM’s are failing to start saying  “Unable to create a deployment for VM[User|host13i1], Please check the affinity groups provided, there may not be sufficient capacity to follow them”
>  
>  
> =====================================================
>  
>  
> 2013-08-31 20:33:16,949 WARN  [vmware.resource.VmwareResource] (DirectAgent-452:10.102.192.13) StartCommand failed due to Exception: java.lang.RuntimeException
> Message: Invalid configuration for device '0'.
>  
> java.lang.RuntimeException: Invalid configuration for device '0'.
>         at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(VmwareClient.java:378)
>         at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:835)
>         at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.tearDownDevices(VirtualMachineMO.java:1643)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2675)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:519)
>         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-08-31 20:33:16,952 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-452:null) Seq 12-1859846507: Response Received:
> 2013-08-31 20:33:16,953 DEBUG [agent.transport.Request] (DirectAgent-452:null) Seq 12-1859846507: Processing:  { Ans: , MgmtId: 227594284004867, via: 12, Ver: v1, Flags: 110, [{"com.cloud.agent.api.StartAnswer":{"vm":{"id":38,"name":"i-3-38-VM","bootloader":"HVM","type":"User","cpus":1,"minSpeed":200,"maxSpeed":200,"minRam":536870912,"maxRam":536870912,"hostName":"host13i1","arch":"x86_64","os":"CentOS 5.3 (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"425de971cf2ec463","params":{"nicAdapter":"E1000","vmware.reserve.cpu":"false","nestedVirtualizationFlag":"false","Message.ReservedCapacityFreed.Flag":"false","rootDiskController":"ide","vmware.reserve.mem":"false"},"uuid":"d51c5b43-0201-4095-8b4c-643df2b2f4e2","disks":[{"data":{"org.apache.cloudstack.storage.to.VolumeObjectTO":{"uuid":"499111c0-9bb3-4921-a370-0c8f5de8579b","volumeType":"ROOT","dataStore":{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":{"uuid":"5bf1f4d7-b301-39f1-85dc-c0af114d68b4","id":203,"poolType":"NetworkFilesystem","host":"10.102.192.100","path":"/cpg_vol/sailaja/zwps1","port":2049}},"name":"ROOT-38","size":2147483648,"path":"ROOT-38-000003","volumeId":47,"vmName":"i-3-38-VM","accountId":3,"chainInfo":"{\"diskDeviceBusName\":\"ide0:1\",\"diskChain\":[\"[5bf1f4d7b30139f185dcc0af114d68b4] i-3-38-VM/ROOT-38.vmdk\",\"[5bf1f4d7b30139f185dcc0af114d68b4] 56c533304ae43a5dbba19a88ee7cea6c/56c533304ae43a5dbba19a88ee7cea6c.vmdk\"]}","format":"OVA","id":47,"hypervisorType":"VMware"}},"diskSeq":0,"type":"ROOT"},{"data":{"org.apache.cloudstack.storage.to.TemplateObjectTO":{"id":0,"format":"ISO","accountId":0,"hvm":false}},"diskSeq":3,"type":"ISO"}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"afb05fee-a8d8-40ee-81f0-bf10dc37bd0a","ip":"10.1.1.84","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:52:59:00:03","dns1":"10.103.128.15","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://789","isolationUri":"vlan://789","isSecurityGroupEnabled":false,"name":"vSwitch1"}]},"result":false,"details":"StartCommand failed due to Exception: java.lang.RuntimeException\nMessage: Invalid configuration for device '0'.\n","wait":0}}] }
> 2013-08-31 20:33:16,959 DEBUG [agent.transport.Request] (Job-Executor-32:job-115 = [ 01c77ff2-ecda-4c31-a308-a1bb4b79f006 ]) Seq 12-1859846507: Received:  { Ans: , MgmtId: 227594284004867, via: 12, Ver: v1, Flags: 110, { StartAnswer } }
> 2013-08-31 20:33:16,961 DEBUG [agent.manager.AgentAttache] (DirectAgent-452:null) Seq 12-1859846507: No more commands found
> 2013-08-31 20:33:16,964 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-32:job-115 = [ 01c77ff2-ecda-4c31-a308-a1bb4b79f006 ]) Unable to start VM on Host[-12-Routing] due to StartCommand failed due to Exception: java.lang.RuntimeException
> Message: Invalid configuration for device '0'.
>  
>  
>  
> 2013-08-31 20:33:17,514 INFO  [user.vm.StartVMCmd] (Job-Executor-32:job-115 = [ 01c77ff2-ecda-4c31-a308-a1bb4b79f006 ]) com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|host13i1]Scope=interface com.cloud.dc.DataCenter; id=2
> 2013-08-31 20:33:17,514 INFO  [user.vm.StartVMCmd] (Job-Executor-32:job-115 = [ 01c77ff2-ecda-4c31-a308-a1bb4b79f006 ]) Unable to create a deployment for VM[User|host13i1], Please check the affinity groups provided, there may not be sufficient capacity to follow them
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[User|host13i1]Scope=interface com.cloud.dc.DataCenter; id=2
>         at com.cloud.vm.VirtualMachineManagerImpl.advanceStart(VirtualMachineManagerImpl.java:842)
>         at com.cloud.vm.VirtualMachineManagerImpl.start(VirtualMachineManagerImpl.java:578)
>         at org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.deployVirtualMachine(VMEntityManagerImpl.java:237)
>         at org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.deploy(VirtualMachineEntityImpl.java:209)
>         at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:3406)
>         at com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:1948)
>         at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
>         at org.apache.cloudstack.api.command.user.vm.StartVMCmd.execute(StartVMCmd.java:120)
>         at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
>         at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
>         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.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-08-31 20:33:17,516 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-32:job-115 = [ 01c77ff2-ecda-4c31-a308-a1bb4b79f006 ]) Complete async job-115 = [ 01c77ff2-ecda-4c31-a308-a1bb4b79f006 ], jobStatus: 2, resultCode: 530, result: Error Code: 533 Error text: Unable to create a deployment for VM[User|host13i1], Please check the affinity groups provided, there may not be sufficient capacity to follow them
>  
> ========================================================================

--
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