You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sateesh Chodapuneedi (JIRA)" <ji...@apache.org> on 2013/05/03 07:10:17 UTC
[jira] [Updated] (CLOUDSTACK-2316) Vmware DVSwitch Managed Object
reference not being returned by vCenter
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sateesh Chodapuneedi updated CLOUDSTACK-2316:
---------------------------------------------
Assignee: Sateesh Chodapuneedi
> Vmware DVSwitch Managed Object reference not being returned by vCenter
> ----------------------------------------------------------------------
>
> Key: CLOUDSTACK-2316
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2316
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Environment: Cloudstack master, vCenter 5.x
> Reporter: Venkata Siva Vijayendra Bhamidipati
> Assignee: Sateesh Chodapuneedi
> Fix For: 4.2.0
>
>
> Attempting to add a Vmware Distributed Virtual Switch as part of a vmware cluster is running into an exception stack trace pasted below:
> INFO [vmware.resource.VmwareResource] (DirectAgent-6:10.223.58.3) Prepare network on vmwaredvs P[dvSwitch0,1380,vmwaredvs:untagged] with name prefix: cloud.public
> WARN [vmware.resource.VmwareResource] (DirectAgent-6:10.223.58.3) StartCommand failed due to Exception: com.vmware.vim25.InvalidProperty
> message: []
> com.vmware.vim25.InvalidPropertyFaultMsg:
> 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 sun.proxy.$Proxy95.retrieveProperties(Unknown Source)
> at com.cloud.hypervisor.vmware.util.VmwareClient.getDecendentMoRef(VmwareClient.java:544)
> at com.cloud.hypervisor.vmware.mo.DatacenterMO.getDvSwitchMor(DatacenterMO.java:488)
> at com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:453)
> at com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:2567)
> at com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2338)
> at com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:442)
> 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:1146)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:679)
> INFO [cloud.vm.VirtualMachineManagerImpl] (secstorage-1:) Unable to start VM on Host[-2-Routing] due to StartCommand failed due to Exception: com.vmware.vim25.InvalidProperty
> message: []
> The MOR (managed object reference) for the dvswitch isn't being returned successfully by vCenter, so configuration is failing.
--
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