Mailing-List: contact cloudstack-issues-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Date: Mon, 11 Mar 2013 13:07:12 +0000 (UTC)
From: "Pradeep Soundararajan (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12635535.1362563953090.418369.1363007232894@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: quoted-printable


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1536?page=3Dcom.atla=
ssian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=
=3D13598793#comment-13598793 ]=20

Pradeep Soundararajan commented on CLOUDSTACK-1536:
---------------------------------------------------

I see there is a below permission issue in Kiran=E2=80=99s setup (10.147.38=
.148). The template directory is still holding the root privilege for u+g, =
that is the reason for the permission issue.

sh-4.1$ pwd
/var/cloudstack/mnt/VM/6950196609054.7ecccb79

sh-4.1$ ls -al
total 28
drwxrwxrwx+ 4 cloud cloud 4096 Mar  6 03:16 .
drwxrwxr-x. 6 cloud cloud 4096 Mar  8 22:18 ..
drwxrwx---+ 2 cloud cloud 4096 Mar  6 03:16 systemvm
drwxr-x---+ 3 root  root  4096 Mar  6 02:18 template

I would suggest we can change the template group privilege to =E2=80=98clou=
d=E2=80=99 recursively and can try doing the testing. I will act upon based=
 on the feedback from Kiran.

               =20
> System VM's not creating in Master with VMware setup.
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-1536
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-153=
6
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the defa=
ult.)=20
>          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 o=
bserevd the following error messages.
> 2013-03-06 20:43:38,149 ERROR [vmware.resource.VmwareResource] (DirectAge=
nt-31:10.147.40.9) CreateCommand 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:269)
>         at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.createDisk(Vir=
tualMachineMO.java:944)
>         at com.cloud.hypervisor.vmware.mo.VirtualMachineMO.createDisk(Vir=
tualMachineMO.java:867)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(Vm=
wareResource.java:3951)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.executeReq=
uest(VmwareResource.java:348)
>         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:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolE=
xecutor.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 administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira