cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-2891) Management server gets stuck when we try to add only a single vlan as a range , ex- try to add 615-615
Date Tue, 11 Jun 2013 06:44:20 GMT


ASF subversion and git services commented on CLOUDSTACK-2891:

Commit 7b63894a0a2226c16de6ce2eaa5aa6f62746026c in branch refs/heads/master from [~likithas]
[;h=7b63894 ]

CLOUDSTACK-2891. While adding a new vlan range if the new range extends an existing range
then CS extends the existing range to include the new range.
This is done by checking if the last vlan in the new range is same as the start vlan of any
existing range.
Since for a single vlan the start and the end vlan are the same the check goes to an infinite
loop resulting in a java.lang.OutOfMemoryError: Java heap space error.
Remove the check for a single vlan because if an existing range starts with the single vlan
then it implies that the range already exists

> Management server gets stuck when we try to add only a single vlan as a range , ex- try
to add 615-615
> ------------------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-2891
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Abhinav Roy
>            Assignee: Likitha Shetty
>            Priority: Critical
>             Fix For: 4.2.0
> Steps :
> =============================
> 1. Deploy a CS setup with advanced network zone.
> 2. Goto Infrastructure -> Zone -> Zone-1 -> Physical Network -> Guest and
try to add a vlan range like 100-100 or 200-200 or anything like that
> or 
> Fire this api :
> Observed behaviour :
> ============================
> 1. The UI gets stuck and we need to restart management server to get it to a working
> 2. In the Logs the queryAsyncJobResult API keeps querying the job for a very long time.

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