[jira] [Commented] (CLOUDSTACK-6317) [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010825#comment-14010825
]
ASF subversion and git services commented on CLOUDSTACK-6317:
-
Commit 869b2535b72af3c0f6d77425f1416d245041aa3a in cloudstack's branch
refs/heads/4.3.0-forward from root
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=869b253 ]
Revert CLOUDSTACK-6317 [VMware] Tagged VLAN support broken for
Management/Control/Storage traffic
This reverts commit f0a98baa0c3258954a4fc4424d8c2f22a50d9ed4.
[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)
[jira] [Commented] (CLOUDSTACK-6317) [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010826#comment-14010826
]
ASF subversion and git services commented on CLOUDSTACK-6317:
-
Commit 825929d7e98cbd680c57ff424f987bbb0b0aff62 in cloudstack's branch
refs/heads/4.3.0-forward from ilya
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=825929d ]
CLOUDSTACK-6317 [VMware] Tagged VLAN support broken for
Management/Control/Storage traffic
[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)
[jira] [Commented] (CLOUDSTACK-6317) [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14010751#comment-14010751
]
ASF subversion and git services commented on CLOUDSTACK-6317:
-
Commit f0a98baa0c3258954a4fc4424d8c2f22a50d9ed4 in cloudstack's branch
refs/heads/4.3.0-forward from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f0a98ba ]
CLOUDSTACK-6317 [VMware] Tagged VLAN support broken for
Management/Control/Storage traffic
Check if switch name detected from traffic label for management, storage,
control traffic is null before falling back to default value.
Signed-off-by: Sateesh Chodapuneedi sate...@apache.org
[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)
[jira] [Commented] (CLOUDSTACK-6317) [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13987656#comment-13987656
]
ASF subversion and git services commented on CLOUDSTACK-6317:
-
Commit 5bc72ea25000456b4a479baac8f9e0690794c0d2 in cloudstack's branch
refs/heads/master from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5bc72ea ]
CLOUDSTACK-6317 [VMware] Tagged VLAN support broken for
Management/Control/Storage traffic
Check if switch name detected from traffic label for management, storage,
control traffic is null before falling back to default value.
Signed-off-by: Sateesh Chodapuneedi sate...@apache.org
[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)
[jira] [Commented] (CLOUDSTACK-6317) [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13987659#comment-13987659
]
ASF subversion and git services commented on CLOUDSTACK-6317:
-
Commit ce7a689ae16f5a28b3ad9ff50a7bb19af31df4cf in cloudstack's branch
refs/heads/4.4-forward from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ce7a689 ]
CLOUDSTACK-6317 [VMware] Tagged VLAN support broken for
Management/Control/Storage traffic
Check if switch name detected from traffic label for management, storage,
control traffic is null before falling back to default value.
Signed-off-by: Sateesh Chodapuneedi sate...@apache.org
[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)
[jira] [Commented] (CLOUDSTACK-6317) [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13987912#comment-13987912
]
ASF subversion and git services commented on CLOUDSTACK-6317:
-
Commit 47f5d2862ac827a3722680fe4f8f1f576776f81b in cloudstack's branch
refs/heads/4.4 from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=47f5d28 ]
CLOUDSTACK-6317 [VMware] Tagged VLAN support broken for
Management/Control/Storage traffic
Check if switch name detected from traffic label for management, storage,
control traffic is null before falling back to default value.
Signed-off-by: Sateesh Chodapuneedi sate...@apache.org
[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)
[jira] [Commented] (CLOUDSTACK-6317) [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13977613#comment-13977613
]
ilya musayev commented on CLOUDSTACK-6317:
--
[~htrippaers] Hugo, this commit caused issues described above, in the nutshell,
it does not read the contents of network label in cloud db fro vmware, it fails
to identify the vSwitch user specified and assumes vSwitch0. It also ignores
the user defined vlan tag - i could confirm this on public and storage networks
- others could also be affected.
What would be an impact of rolling back this commit - are there any dependency
or is this an enhancement?
[~sateeshc] [~ramg]
How far are we from the fix? We are Citrix supported customer and kindly asked
for escalation on this issue.
Thank you,
ilya
[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)
[jira] [Commented] (CLOUDSTACK-6317) [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970179#comment-13970179
]
Ram Ganesh commented on CLOUDSTACK-6317:
Sateesh is testing the fix. Should have an update in another couple of days.
[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)
[jira] [Commented] (CLOUDSTACK-6317) [VMware] Tagged VLAN support broken for Management/Control/Storage traffic
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13956314#comment-13956314
]
Sateesh Chodapuneedi commented on CLOUDSTACK-6317:
--
If admin configures zone with tagged VLAN for management/storage traffic then
system vms would fail to get created.
[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)
