We found this bug in ACS 4.3 Release. Seems there are some mistaken in dvSwitch-related codes. Maybe the codes are not well-tested?
------------------ hubo 2014-04-17 ------------------------------------------------------------- 发件人：ilya musayev <[email protected]> 发送日期：2014-04-17 15:29 收件人：users 抄送： 主题：Re: Vmware 5.5 dvSwitch support. What version of ACS is this affecting? On 4/16/14, 3:38 PM, Willard Rathjen wrote: > It looks like the CS does not like the formatting of the network label, > causing it to not parse the VLAN ID correctly. As a quick test can you change > the label to "dvSwitchtest,602,vmwaredvs”. It’s a long shot, but easy enough > to test. > > > > 491 /** > 492 * Nicira NVP requires all vms to be connected to a single > port-group. > 493 * A unique vlan needs to be set per port. This vlan is > specific to > 494 * this implementation and has no reference to other vlans > in CS > 495 */ > 496 networkName = "br-int"; // FIXME Should be set via a > configuration item in CS > 497 // No doubt about this, depending on vid=null to avoid lots > of code below > 498 vid = null; > 499 } else { > 500 networkName = composeCloudNetworkName(namePrefix, vlanId, > secondaryvlanId, networkRateMbps, physicalNetwork); > 501 > 502 if(vlanId != null && > !UNTAGGED_VLAN_NAME.equalsIgnoreCase(vlanId)) { > 503 createGCTag = true; > 504 vid = Integer.parseInt(vlanId); > 505 } > 506 if (secondaryvlanId != null) { > 507 spvlanid = Integer.parseInt(secondaryvlanId); > 508 } > 509 } > > > Willard Rathjen > Cloud Systems Engineer > > Office +1.800.735.7104 | Direct +1.515.612.7813 > [email protected] | www.appcore.com > > ---------------------------------------------------------------------- > The information in this message is intended for the named recipients only. It > may contain information that is privileged, confidential or otherwise > protected from disclosure. If you are not the intended recipient, you are > hereby notified that any disclosure, copying, distribution, or the taking of > any action in reliance on the contents of this message is strictly > prohibited. If you have received this e-mail in error, do not print it or > disseminate it or its contents. In such event, please notify the sender by > return e-mail and delete the e-mail file immediately thereafter. Thank you. > > > > On Apr 16, 2014, at 9:28 AM, Steve Searles <[email protected]> wrote: > >> Anyone know why this may be happening? vmware.use.dvswitch is set to true in >> global settings. The management server has been restarted. >> >> >> The network label I am using is "dvSwitch-test,602,vmwaredvs" Using a >> standard vSwitch works fine. e.g. vSwitch1,602,vmwaresvs Any ideas? >> >> 2014-04-03 12:39:45,313 DEBUG [c.c.h.v.r.VmwareResource] >> (DirectAgent-391:ctx-ed1b98f6 >> esx02.cs.zimcom.net<http://esx02.cs.zimcom.net>) VM i-2-40-VM will be >> started with NIC device type: E1000 >> 2014-04-03 12:39:45,313 INFO [c.c.h.v.r.VmwareResource] >> (DirectAgent-391:ctx-ed1b98f6 >> esx02.cs.zimcom.net<http://esx02.cs.zimcom.net>) Prepare NIC device based on >> NicTO: >> {"deviceId":0,"networkRateMbps":200,"defaultNic":true,"uuid":"9ef9f0ff-70e4-4851-8030-edef22aa61df","ip":"172.17.2.95","netmask":"255.255.255.0","gateway":"172.17.2.1","mac":"02:00:5a:92:00:0d","dns1":"209.212.245.10","dns2":"209.212.246.10","broadcastType":"Vlan","type":"Guest","broadcastUri":"vlan://610","isolationUri":"vlan://610","isSecurityGroupEnabled":false,"name":"dvSwitch-test,602,vmwaredvs"} >> 2014-04-03 12:39:45,318 INFO [c.c.h.v.r.VmwareResource] >> (DirectAgent-391:ctx-ed1b98f6 >> esx02.cs.zimcom.net<http://esx02.cs.zimcom.net>) Prepare network on >> vmwaredvs dvSwitch-test with name prefix: cloud.guest >> 2014-04-03 12:39:45,325 WARN [c.c.h.v.r.VmwareResource] >> (DirectAgent-391:ctx-ed1b98f6 >> esx02.cs.zimcom.net<http://esx02.cs.zimcom.net>) StartCommand failed due to >> Exception: java.lang.NumberFormatException >> Message: null >> >> java.lang.NumberFormatException: null >> at java.lang.Integer.parseInt(Integer.java:443) >> at java.lang.Integer.parseInt(Integer.java:514) >> at >> com.cloud.hypervisor.vmware.mo.HypervisorHostHelper.prepareNetwork(HypervisorHostHelper.java:504) >> at >> com.cloud.hypervisor.vmware.resource.VmwareResource.prepareNetworkFromNicInfo(VmwareResource.java:3692) >> at >> com.cloud.hypervisor.vmware.resource.VmwareResource.execute(VmwareResource.java:2934) >> at >> com.cloud.hypervisor.vmware.resource.VmwareResource.executeRequest(VmwareResource.java:525) >> at >> com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) >> at >> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) >> at >> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56) >> at >> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103) >> at >> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53) >> at >> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46) >> 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:701) >> >> >> >> vmware 5.5 >> dvswitch 5.5 >> centos 6.4 non-oss rpm build. >> >> >> >> Steven Searles, CTO | [email protected] >> Zimcom Internet Solutions | www.zimcom.net >> O: 513.231.9500 | D: 513.233.4130 >> >> >> >
