[
https://issues.apache.org/jira/browse/CLOUDSTACK-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603376#comment-13603376
]
Sateesh Chodapuneedi commented on CLOUDSTACK-1536:
--------------------------------------------------
Had a look at Kiran's setup and this is how I resolved locally in his setup
- Tried to remove the primary store using UI and this failed because of bug
1426 (please note 1426 might be fixed in later builds post build 101)
- Removed the DB entry for this primary store from the storage_pool table
- Added a new primary store using the UI
- Now the System VM templates are downloaded and provisioned
According to me the root cause for all of these issues is the "premission
denied" issue we ran into initally. TemplateDownloadManager failed to download
the template after 3 retries(with root being the owner of the template
directory) and hence the download of systemvm template never happened later.
Once the folder permission was manually modified further errors(see below) are
encountered which again is because of absence of systemvm template
The configuration error mentioned in this bug description is just an
implication of system vm template download failure.
It's because path of volume (that is being prepared in datastore) for that
specific volume is NULL in volumes table.
Log message :====
java.lang.RuntimeException: Invalid configuration for device '0'.
===============
volumes table contents:-
mysql> select id,name,path from volumes;
+----+---------+------------+
| id | name | path |
+----+---------+------------+
| 37 | ROOT-37 | NULL |
| 38 | ROOT-38 | NULL |
| 39 | ROOT-39 | ROOT-39-39 |
| 40 | ROOT-40 | ROOT-40-40 |
+----+---------+------------+
Attempt to prepare a virtual disk on datastore fails for all the volumes with
path as NULL.This is expected.
And system vm template download failure is due to permission issues. Seems
ticket CLOUDSTACK-1228 is to address the permissions issue.
Per Chandan's latest comment in bug 1228 we should root cause why this issue is
showing up only in Kiran's setup. Kiran can you investigate
> 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: Sateesh Chodapuneedi
> 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
