cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitin Mehta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-3778) [VMware] SSVM VM fails to create for the first time with message "specified key already exists".
Date Thu, 25 Jul 2013 10:55:48 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nitin Mehta updated CLOUDSTACK-3778:
------------------------------------

    Summary: [VMware]  SSVM VM fails to create for the first time with message "specified
key already exists".  (was: SSVM VM fails to create for the first time with message "specified
key already exists".)
    
> [VMware]  SSVM VM fails to create for the first time with message "specified key already
exists".
> -------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3778
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3778
>             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
>         Environment: VMware
>            Reporter: Kiran Koneti
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: management-server.zip
>
>
> When we try to create a Advanced Zone setup when the first SSVM tries to come up the
Vcenter says 'The specified key, name, or identifier already exists." and the SSVM creation
fails for the first time and later then the SSVM comes up with another name s-3-vm.
> The steps are as follows:
> 1)Installed the CS using the latest build.
> 2)Added a host which is freshly installed to the cluster in the VCenter.
> 3)Added the Vcenter details to the CS and the setup started creating the system VM's.
> 4)Once the root volume is created for the SSVM the VM named "s-1-vm" created.
> 5)Then the VM gets deleted before it is powered on throwing the error message as below
> "2013-07-24 20:26:51,680 WARN  [vmware.resource.VmwareResource] (DirectAgent-8:10.147.40.18)
StartCommand failed due to Exception: com.vmware.vim25.AlreadyExists
> message: []
> com.vmware.vim25.AlreadyExistsFaultMsg: The specified key, name, or identifier already
exists.
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>         at java.lang.reflect.Constructor.newInstance(Constructor.java:532)
>         at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:130)
>         at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108)
>         at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78)
>         at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:107)
>         at $Proxy90.addPortGroup(Unknown Source)
>         at com.cloud.hypervisor.vmware.mo.HostNetworkSystemMO.addPortGroup(HostNetworkSystemMO.java:38)
>         at com.cloud.hypervisor.vmware.mo.HostMO.createPortGroup(HostMO.java:389)
>         at com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:961)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:3149)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2775)
>         at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:520)
>         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)"
> 6)Later it creates the root volume for one more SSVM and then the s-3-vm comes up without
any issues.
> 7)all the system VM functionalities are normal.
> Attaching the Management server 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

Mime
View raw message