You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Kiran Koneti (JIRA)" <ji...@apache.org> on 2013/06/27 07:21:20 UTC

[jira] [Created] (CLOUDSTACK-3223) Excertion occured while creating the CPVM in the VmWare Setup using the latest SystemVM template.

Kiran Koneti created CLOUDSTACK-3223:
----------------------------------------

             Summary: Excertion occured while creating the CPVM in the VmWare Setup using the latest SystemVM template.
                 Key: CLOUDSTACK-3223
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3223
             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
            Priority: Critical
             Fix For: 4.2.0


Excertion occured while creating the CPVM in the VmWare Setup using the latest SystemVM template, below are the steps followed.

1)Tried to create a VMware Advanced Zone  setup using the latest system VM templates for VH7.
2)while creating the CPVM the below error message is observed:

"2013-06-26 16:30:57,550 INFO  [vmware.resource.VmwareResource] (DirectAgent-3:10.147.40.18) Prepare network on vmwaresvs P[vSwitch0:untagged] with name prefix: cloud.public
2013-06-26 16:30:57,826 WARN  [vmware.resource.VmwareResource] (DirectAgent-3: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:382)
        at com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:866)
        at com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:2853)
        at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2617)
        at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:474)
        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)"

3)The same error message is also observed in the Vcenter also for both 4.1 and 5.0 setups.

Note:This error message does not prevent the creation of CPVM or any other functionality of CS,but this would create a panic while creating the setup.

--
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