Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 27 Jun 2013 11:10:19 +0000 (UTC)
From: "Sanjeev N (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12655119.1372331160033.179214.1372331419911@arcas>
In-Reply-To: <JIRA.12655119.1372331160033@arcas>
References: <JIRA.12655119.1372331160033@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-3234) [VM_Snapshot] Starting VM fails
 if VM snapshot is created from the VM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3234?page=3Dcom.atl=
assian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sanjeev N updated CLOUDSTACK-3234:
----------------------------------

    Attachment: management-server.rar

Management server log file attached.
               =20
> [VM_Snapshot] Starting VM fails if VM snapshot is created from the VM
> ---------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3234
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-323=
4
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          Components: Snapshot
>    Affects Versions: 4.2.0
>         Environment: Latest build from master-6-17-stable branch
>            Reporter: Sanjeev N
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: management-server.rar
>
>
> [VM_Snapshot] Starting VM fails if VM snapshot is created from the VM
> Steps to Reproduce:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> 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:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Starting VM Should succeed
> Actual Behavior:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Starting VM failed
> Observations:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> 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] (DirectAge=
nt-44:10.147.40.18) StartCommand failed due to Exception: java.lang.Runtime=
Exception
> Message: Invalid configuration for device '0'.
> java.lang.RuntimeException: Invalid configuration for device '0'.
>         at com.cloud.hypervisor.vmware.util.VmwareClient.waitForTask(Vmwa=
reClient.java:291)
>         at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.configureVm(Vi=
rtualMachineMO.java:832)
>         at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.tearDownDevice=
s(VirtualMachineMO.java:1635)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(Vm=
wareResource.java:2403)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.executeReq=
uest(VmwareResource.java:474)
>         at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgen=
tAttache.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$ScheduledFutu=
reTask.access$101(ScheduledThreadPoolExecutor.java:165)
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutu=
reTask.run(ScheduledThreadPoolExecutor.java:266)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolEx=
ecutor.java:1146)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolE=
xecutor.java:615)
>         at java.lang.Thread.run(Thread.java:679)
> 2013-06-27 12:24:47,300 DEBUG [agent.manager.DirectAgentAttache] (DirectA=
gent-44:null) Seq 10-1663500505: Response Received:
> 2013-06-27 12:24:47,302 DEBUG [agent.transport.Request] (DirectAgent-44:n=
ull) Seq 10-1663500505: Processing:  { Ans: , MgmtId: 7332683579487, via: 1=
0, Ver: v1, Flags: 10, [{"StartAnswer":{"vm":{"id":35,"name":"i-2-35-VM","b=
ootloader":"HVM","type":"User","cpus":1,"minSpeed":500,"maxSpeed":500,"minR=
am":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","nestedVi=
rtualizationFlag":"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":21474=
83648,"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":"7e=
d57c44-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.1=
28.16","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://33","is=
olationUri":"vlan://33","isSecurityGroupEnabled":false}]},"result":false,"d=
etails":"StartCommand failed due to Exception: java.lang.RuntimeException\n=
Message: 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-E=
xecutor-149:job-149) Unable to start VM on Host[-10-Routing] due to StartCo=
mmand 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 administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira