[CLOUDSTACK-3223] Exception observed while creating CPVM in VMware Setup with DVS

• Type: Bug
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.2.0
• Fix Version/s: 4.9.2.0
• Component/s: Install and Setup
• Security Level: Public (Anyone can view this level - this is the default.)
• Assignee: Sateesh Chodapuneedi
• Reporter: Kiran Koneti
• Created: 27/Jun/13 05:21
• Updated: 17/May/17 06:31

Description

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

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

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.

Issue Links

• links to: GitHub Pull Request #1872