[
https://issues.apache.org/jira/browse/CLOUDSTACK-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705731#comment-13705731
]
Sateesh Chodapuneedi commented on CLOUDSTACK-3468:
--------------------------------------------------
Can this can be downgraded to major/critical per following?
1) Mixed vswitch environment is not common scenario. In general users would
setup cloudstack over a particular type of vswitch, standard / distributed
vswitch.
2) We have work around fo this. Work around is to create/change vswitch with
same name as that of dvswitch mentioned in physical network traffic type.
> Failed to create Guest port groups while deploying instances with Mixed
> VMWARE clusters of different switches with which instances are failed to
> deploy (Default - DVS, second cluster- StandardvSwitch)
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3468
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3468
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.2.0
> Reporter: Sailaja Mada
> Assignee: Sateesh Chodapuneedi
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: apilog.log.2013-07-09.gz,
> management-server.log.2013-07-09
>
>
> Setup :
> Two VMWARE clusters : Cluster1 is with DVS , Cluster2 is with Standard switch
> 1. Enable vmware.use.dvswitch to true
> 2. Configure Zone with with
> a)Physical network 1 with Mgmt traffic - With Label as vSwitch0
> b)Physical network 2 with guest & public traffic - Label as
> newdv1,,vmwaredvs
> 3. Add Cluster 1 during Zone deployment without overriding Public/Guest
> traffic as the labels are configured at the zone level
> 4. Create new account and deploy VM's on DVS Enabled cluster
> 5. Add second cluster with Standard switch specifying the traffic label as
> vSwitch0 with override option selected with Standard switch.
> 6. Update host tag to the host added under this cluster
> 7. Tried to deploy new VM under this cluster - I already have one instance
> and Router with Account 1 with this guestnetwork created with DVS cluster.
> Now I am trying to create one more instance on standard switch cluster using
> host TAGS.
> Observation:
> Failed to create Guest port groups while deploying instances with Mixed
> VMWARE clusters of different switches with which instances are failed to
> deploy (Default - DVS, second cluster- StandardvSwitch)
> Instance is failing to start :
> 2013-07-09 20:19:58,948 INFO [vmware.resource.VmwareResource]
> (DirectAgent-49:10.102.192.23) Prepare NIC device based on NicTO:
> {"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"2bb4d376-99e8-449b-9b18-ec2f6887daf6","ip":"10.1.1.144","netmask":"255.255.255.0","gateway":"10.1.1.1","mac":"02:00:79:e9:00:04","dns1":"10.103.128.15","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://792","isolationUri":"vlan://792","isSecurityGroupEnabled":false,"name":"newdv1,,vmwaredvs"}
> 2013-07-09 20:19:58,953 INFO [vmware.resource.VmwareResource]
> (DirectAgent-49:10.102.192.23) Prepare network on vmwaresvs
> P[newdv1:untagged] with name prefix: cloud.guest
> 2013-07-09 20:19:58,981 ERROR [vmware.mo.HypervisorHostHelper]
> (DirectAgent-49:10.102.192.23) Unable to find vSwitchnewdv1
> 2013-07-09 20:19:58,981 WARN [vmware.resource.VmwareResource]
> (DirectAgent-49:10.102.192.23) StartCommand failed due to Exception:
> java.lang.Exception
> Message: Unable to find vSwitchnewdv1
> java.lang.Exception: Unable to find vSwitchnewdv1
> at
> com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:830)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:2923)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2687)
> at
> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:479)
> 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)
> 2013-07-09 20:19:58,983 DEBUG [agent.manager.DirectAgentAttache]
> (DirectAgent-49:null) Seq 7-1447821361: Response Received
--
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
