incubator-cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sateesh Chodapuneedi (JIRA)" <>
Subject [jira] [Resolved] (CLOUDSTACK-1491) Failed to addCluster for Vmware.
Date Sun, 03 Mar 2013 07:43:12 GMT


Sateesh Chodapuneedi resolved CLOUDSTACK-1491.

    Resolution: Fixed

A check for physical network configuration with multiple virtual switches is looking if a
physical network is shared by multiple type of virtual switches or not. This check fails for
public traffic in case of basic zone, because basic zone contains only 1 network which is
shared. Hence skipping the check in case of basic zone.

Commit details of the fix below.

Updated Branches:
  refs/heads/master 6a1ecae55 -> 7c52d7d1c

In basic zone, skip checks for physical network configuration with multiple virtual switches.

Signed-off-by: Sateesh Chodapuneedi <>


Branch: refs/heads/master
Commit: 7c52d7d1c92e57335958cd43f5185481043eb1aa
Parents: 6a1ecae
Author: Sateesh Chodapuneedi <>
Authored: Sun Mar 3 08:22:40 2013 +0530
Committer: Sateesh Chodapuneedi <>
Committed: Sun Mar 3 08:22:40 2013 +0530

> Failed to addCluster for Vmware.
> --------------------------------
>                 Key: CLOUDSTACK-1491
>                 URL:
>             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: Min Chen
>            Assignee: Sateesh Chodapuneedi
>            Priority: Blocker
>             Fix For: 4.2.0
> With lastest master branch code, addCluster failed with the following stack trace:
> 2013-03-01 17:34:18,953 DEBUG [] (552681680@qtp-144013098-6:null)
Failed to retrieve the default label for public 1 hypervisor: VMware due to:
Unable to find the default physical network with traffic=Public in zone id=1.
> 2013-03-01 17:34:19,305 ERROR [cloud.api.ApiServer] (552681680@qtp-144013098-6:null)
unhandled exception executing api command: addCluster
> java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
>         at java.util.ArrayList.rangeCheck(
>         at java.util.ArrayList.get(
>         at
>         at net.sf.cglib.proxy.MethodProxy.invoke(
>         at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(
>         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
>         at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(
>         at
>         at sun.reflect.GeneratedMethodAccessor46.invoke(Unknown Source)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> This exception is thrown from this piece of code recently checked in related to Vmware
Distributed Vswitch feature:
>         List<? extends PhysicalNetwork> pNetworkListGuestTraffic = _netmgr.getPhysicalNtwksSupportingTrafficType(dcId,
>         List<? extends PhysicalNetwork> pNetworkListPublicTraffic = _netmgr.getPhysicalNtwksSupportingTrafficType(dcId,
>         // Public network would be on single physical network hence getting first object
of the list would suffice.
>         PhysicalNetwork pNetworkPublic = pNetworkListPublicTraffic.get(0);
> In this case, pNetworkListPublicTraffic list is empty, thus index out of range error
is thrown next. 

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:

View raw message