[
https://issues.apache.org/jira/browse/CLOUDSTACK-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598682#comment-13598682
]
Pradeep Soundararajan commented on CLOUDSTACK-1536:
---------------------------------------------------
Kiran, could you please try as per Sangeetha's comment as per #1228:
>> Sangeetha Hariharan added a comment - 27/Feb/13 07:55
>> In my case , I delete the existing cloud user in my management sever:
>> userdel cloud
>> Then attempted a fresh installation.
>> I did not face issue with Systemvm keypairs generation anymore.
>> Kiran , you could try deleting the cloud user and attempting a fresh install
>> on the same box to see if this issue you are facing is resolved.
Also, please try with the latest Master build.
> 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
