cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sateesh Chodapuneedi (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-6317) [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
Date Tue, 01 Apr 2014 09:44:18 GMT
Sateesh Chodapuneedi created CLOUDSTACK-6317:
------------------------------------------------

             Summary: [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
                 Key: CLOUDSTACK-6317
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6317
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: VMware
    Affects Versions: 4.3.0, 4.4.0
         Environment: VMware vCenter 5.1, ESXi 5.0 hosts
MS with ACS 4.3.0
            Reporter: Sateesh Chodapuneedi
            Assignee: Sateesh Chodapuneedi
            Priority: Critical
             Fix For: 4.4.0, 4.3.1


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: {"deviceId":0,"networkRateMbps":-1,"defaultNic":false,"uuid":"07c38800-6da3-4596-b0ea-09047d45970e","mac":"02:00:63:46:00:02","broadcastType":"LinkLocal","type":"Control","isSecurityGroupEnabled":false,"name":"vSwitch0,100"}
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




--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message