Mailing-List: contact cloudstack-issues-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Tue, 12 Mar 2013 10:31:13 +0000 (UTC)
From: "Sateesh Chodapuneedi (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12635535.1362563953090.424923.1363084273298@arcas>
In-Reply-To: <JIRA.12635535.1362563953090@arcas>
References: <JIRA.12635535.1362563953090@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-1536) System VM's not creating in
 Master with VMware setup.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13599897#comment-13599897 ] 

Sateesh Chodapuneedi commented on CLOUDSTACK-1536:
--------------------------------------------------

System VM template is not downloaded to primary storage pool due to permissions issue mentioned in above comments.
Is this resolved now? 
Is system VM template downloaded successfully after permissions are updated manually or through cloud spec file?
                
> System VM's not creating in Master with VMware setup.
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-1536
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1536
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Install and Setup
>    Affects Versions: 4.2.0
>            Reporter: Kiran Koneti
>            Assignee: Pradeep Soundararajan
>            Priority: Blocker
>             Fix For: 4.2.0
>
>
> Created a VMware Advanced Zone setup and while creating the system Vm's obserevd the following error messages.
> 2013-03-06 20:43:38,149 ERROR [vmware.resource.VmwareResource] (DirectAgent-31:10.147.40.9) CreateCommand 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:269)
>         at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.createDisk(VirtualMachineMO.java:944)
>         at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.createDisk(VirtualMachineMO.java:867)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:3951)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:348)
>         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)
> Attaching the MS 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