You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Sateesh Chodapuneedi (JIRA)" <ji...@apache.org> on 2013/03/01 12:49:12 UTC

[jira] [Resolved] (CLOUDSTACK-1467) Failed to create Volume for the System Vm's.

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

Sateesh Chodapuneedi resolved CLOUDSTACK-1467.
----------------------------------------------

    Resolution: Not A Problem

Resolving this as not a problem because it's a setup issue.
Datastore is found to be empty. Hence the system vm template doesn't have it's files accompanied by. Create volume attempt fails because there is no image file available to clone from.
Also found following events in datastore history.

Removed datastore 
b5664dd04a133f28b4c121d602b2b26e 
from 10.147.40.22
28-02-2013 11:04:40
Administrator

Discovered datastore 
b5664dd04a133f28b4c121d602b2b26e 
on 10.147.40.22
info
01-03-2013 12:32:53

                
> Failed to create Volume for the System Vm's.
> --------------------------------------------
>
>                 Key: CLOUDSTACK-1467
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1467
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Install and Setup
>    Affects Versions: 4.1.0
>         Environment: VMware
>            Reporter: Kiran Koneti
>            Assignee: Sateesh Chodapuneedi
>            Priority: Blocker
>             Fix For: 4.1.0
>
>         Attachments: management-server.zip
>
>
> Used the latest CS Build.Failed to create Volume for the system VM's with the old system VM templates with the following error message:
> 2013-03-01 18:00:36,756 DEBUG [cloud.storage.StorageManagerImpl] (consoleproxy-1:null) Creating volume: Vol[2|vm=2|ROOT]
> 2013-03-01 18:00:36,756 DEBUG [cloud.storage.StorageManagerImpl] (consoleproxy-1:null) Trying to create in Pool[200|NetworkFilesystem]
> 2013-03-01 18:00:36,771 DEBUG [cloud.template.TemplateManagerImpl] (consoleproxy-1:null) Template 8 has already been downloaded to pool 200
> 2013-03-01 18:00:36,780 DEBUG [agent.transport.Request] (consoleproxy-1:null) Seq 1-410910733: Waiting for Seq 410910732 Scheduling:  { Cmd , MgmtId: 7614406590488, via: 1, Ver: v1, Flags: 100111, [{"storage.CreateCommand":{"volId":2,"pool":{"id":200,"uuid":"b5664dd0-4a13-3f28-b4c1-21d602b2b26e","host":"10.147.28.7","path":"/export/home/kiran/primary2","port":2049,"type":"NetworkFilesystem"},"diskCharacteristics":{"size":0,"tags":[],"type":"ROOT","name":"ROOT-2","useLocalStorage":false,"recreatable":true,"diskOfferingId":10,"volumeId":2,"hyperType":"VMware"},"templateUrl":"eb4ff707bf443bdd81604fefd374659e","wait":0}}] }
> 2013-03-01 18:00:36,906 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 0 routers to update status.
> 2013-03-01 18:00:36,908 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-03-01 18:00:36,986 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 0 routers to update status.
> 2013-03-01 18:00:36,988 DEBUG [network.router.VirtualNetworkApplianceManagerImpl] (RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
> 2013-03-01 18:00:41,134 INFO  [vmware.mo.DatastoreMO] (DirectAgent-7:10.147.40.22) Folder ROOT-1-1 does not exist on datastore
> 2013-03-01 18:00:41,134 INFO  [vmware.resource.VmwareResource] (DirectAgent-7:10.147.40.22) create linked clone from template
> 2013-03-01 18:00:43,002 ERROR [vmware.mo.VirtualMachineMO] (DirectAgent-7:10.147.40.22) VMware cloneVM_Task failed due to File [b5664dd04a133f28b4c121d602b2b26e] eb4ff707bf443bdd81604fefd374659e/eb4ff707bf443bdd81604fefd374659e-Snapshot1.vmsn was not found com.vmware.vim25.FileNotFound
> 2013-03-01 18:00:43,002 ERROR [vmware.resource.VmwareResource] (DirectAgent-7:10.147.40.22) Unable to clone from the template
> 2013-03-01 18:00:43,002 ERROR [vmware.resource.VmwareResource] (DirectAgent-7:10.147.40.22) CreateCommand failed due to Exception: java.lang.Exception
> Message: Unable to clone from the template
> java.lang.Exception: Unable to clone from the template
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3845)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:335)
>         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-03-01 18:00:43,005 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-7:null) Seq 1-410910732: Response Received:
> Attaching the management serevr logs.

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