cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjeev N (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-3234) [VM_Snapshot] Starting VM fails if VM snapshot is created from the VM
Date Wed, 28 Aug 2013 11:31:51 GMT

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

Sanjeev N closed CLOUDSTACK-3234.
---------------------------------


Verified on the latest build git rev-parse HEAD~5
1f46bc3fb09aead2cf1744d358fea7adba7df6e1. Works fine.
                
> [VM_Snapshot] Starting VM fails if VM snapshot is created from the VM
> ---------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3234
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3234
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Snapshot, VMware
>    Affects Versions: 4.2.0
>         Environment: Latest build from master-6-17-stable branch
>            Reporter: Sanjeev N
>            Assignee: Mice Xia
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: cloud.dmp, management-server.rar, management-server.rar
>
>
> [VM_Snapshot] Starting VM fails if VM snapshot is created from the VM
> Steps to Reproduce:
> ==================
> 1.Bring up CS in advanced zone using VMWare cluster
> 2.Deploy guest vm using default centOS template
> 3.Go to Instance and take "VM Snapshot"
> 4.After vm snapshot completion stop the vm
> 5.Try to Start it
> Expected Result:
> ==============
> Starting VM Should succeed
> Actual Behavior:
> =============
> Starting VM failed
> Observations:
> ============
> Starting VM was successful only after deleting the vm snapshot created in step3.
> Found following exceptions while trying to start the vm with vm snapshot present:
> 2013-06-27 12:24:47,298 WARN  [vmware.resource.VmwareResource] (DirectAgent-44:10.147.40.18)
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:291)
>         at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(VirtualMachineMO.java:832)
>         at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.tearDownDevices(VirtualMachineMO.java:1635)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2403)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:474)
>         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:1146)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-06-27 12:24:47,300 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-44:null)
Seq 10-1663500505: Response Received:
> 2013-06-27 12:24:47,302 DEBUG [agent.transport.Request] (DirectAgent-44:null) Seq 10-1663500505:
Processing:  { Ans: , MgmtId: 7332683579487, via: 10, Ver: v1, Flags: 10, [{"StartAnswer":{"vm":{"id":35,"name":"i-2-35-VM","bootloader":"HVM","type":"User","cpus":1,"minSpeed":500,"maxSpeed":500,"minRam":536870912,"maxRam":536870912,"arch":"x86_64","os":"CentOS
5.3 (64-bit)","bootArgs":"","rebootOnCrash":false,"enableHA":false,"limitCpuUse":false,"enableDynamicallyScaleVm":false,"vncPassword":"e927c21f83a67237","params":{"nicAdapter":"E1000","Message.ReservedCapacityFreed.Flag":"false","nestedVirtualizationFlag":"false","rootDiskController":"ide"},"uuid":"aec68383-2123-42ce-80db-219e096ea189","disks":[{"id":35,"name":"ROOT-35","mountPoint":"/export/home/sanjeev/pri_esx_master","path":"ROOT-35-35-000001","size":2147483648,"type":"ROOT","storagePoolType":"NetworkFilesystem","storagePoolUuid":"dbf5c167-d71b-3cb7-896a-f9f2c24bb139","deviceId":0},{"id":35,"name":"ssh-passwd-centOS53","size":0,"type":"ISO","storagePoolType":"ISO","deviceId":3}],"nics":[{"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"7ed57c44-8be2-4169-91a7-9ae9e0618b8b","ip":"10.147.33.14","netmask":"255.255.255.128","gateway":"10.147.33.1","mac":"06:5c:e6:00:00:17","dns1":"10.103.128.16","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://33","isolationUri":"vlan://33","isSecurityGroupEnabled":false}]},"result":false,"details":"StartCommand
failed due to Exception: java.lang.RuntimeException\nMessage: Invalid configuration for device
'0'.\n","wait":0}}] }
> 2013-06-27 12:24:47,302 DEBUG [agent.transport.Request] (Job-Executor-149:job-149) Seq
10-1663500505: Received:  { Ans: , MgmtId: 7332683579487, via: 10, Ver: v1, Flags: 10, { StartAnswer
} }
> 2013-06-27 12:24:47,308 INFO  [cloud.vm.VirtualMachineManagerImpl] (Job-Executor-149:job-149)
Unable to start VM on Host[-10-Routing] due to StartCommand failed due to Exception: java.lang.RuntimeException
> Message: Invalid configuration for device '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

Mime
View raw message