Details
Description
Prior to ACS 4.3.0 CloudStack used to support tagged VLAN for management / storage / control traffic via traffic label, where admin would specify the VLAN in comma separated string of vmware network traffic label. E.g. vSwitch0,100 - This means management traffic would use standard vSwitch port group tagged with VLAN 100 which sits on vSwitch0 existing on ESXi host.
This is functionality was broken since below commit in ACS 4.3 branch,
Commit 7c4831df9292115466fb9e01fcba952a5dad31c1 in branch refs/heads/4.3 from Hugo Trippaers
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7c4831d ]
This commit overwrites the parsed vSwitch name, from traffic label, with traffic label specified by admin resulting into below error during deployment of SSVM (or any VM that needs management/storage traffic)
2014-04-01 08:23:19,866 DEBUG [c.c.h.v.r.VmwareResource] (DirectAgent-9:ctx-862d86ff 10.102.192.3) VM v-2-VM will be started with NIC device type: E1000
2014-04-01 08:23:19,866 INFO [c.c.h.v.r.VmwareResource] (DirectAgent-9:ctx-862d86ff 10.102.192.3) Prepare NIC device based on NicTO:
2014-04-01 08:23:21,150 ERROR [c.c.h.v.m.HypervisorHostHelper] (DirectAgent-6:ctx-a6062e05 10.102.192.3) Unable to find vSwitchvSwitch0,100
2014-04-01 08:23:21,151 WARN [c.c.h.v.r.VmwareResource] (DirectAgent-6:ctx-a6062e05 10.102.192.3) StartCommand failed due to Exception: java.lang.Exception
Message: Unable to find vSwitchvSwitch0,100
Attachments
Issue Links
- is duplicated by
-
CLOUDSTACK-5012 Bad data inserted into physical network labels for Zone Create Wizard using VMWare
- Resolved