[
https://issues.apache.org/jira/browse/CLOUDSTACK-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598793#comment-13598793
]
Pradeep Soundararajan commented on CLOUDSTACK-1536:
---------------------------------------------------
I see there is a below permission issue in Kiran’s 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 ‘cloud’
recursively and can try doing the testing. I will act upon based on the
feedback from Kiran.
> 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
