[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Likitha Shetty updated CLOUDSTACK-3062:
---------------------------------------

    Description: 
1. Create 2 guest VLAN ranges e.g. 360-365 and 370-375.
2. Create 2 accounts acct1 and acct2.
3. Dedicate the first range 360-365 to acct1 and the second range 370-375 to 
acct2.
4. Create a new vlan range 366-369.
5. Now when we try to dedicate range 366-369 to acct1, the range 360-369 gets 
dedicated to acct1 but the dedication of 370-375 to acct2 is removed. 

  was:
Create 2 guest VLAN ranges e.g. 360-365 and 370-375.
Create 2 accounts acct1 and acct2.
Dedicate the first range 360-365 to acct1 and the second range 370-375 to acct2.
Now when we try to dedicate range 366-369 to acct1, the range 360-369 gets 
dedicated to acct1 but the dedication of 370-375 to acct2 is removed. 

    
> Dedication of a guest vlan range that extends 2 ranges dedicated to different 
> accounts removes an old dedication 
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3062
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3062
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>    Affects Versions: 4.2.0
>            Reporter: Likitha Shetty
>            Assignee: Abhinav Roy
>              Labels: integration-test
>             Fix For: 4.2.0
>
>
> 1. Create 2 guest VLAN ranges e.g. 360-365 and 370-375.
> 2. Create 2 accounts acct1 and acct2.
> 3. Dedicate the first range 360-365 to acct1 and the second range 370-375 to 
> acct2.
> 4. Create a new vlan range 366-369.
> 5. Now when we try to dedicate range 366-369 to acct1, the range 360-369 gets 
> dedicated to acct1 but the dedication of 370-375 to acct2 is removed. 

--
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: http://www.atlassian.com/software/jira

Reply via email to