cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3062) Dedication of a guest vlan range that extends 2 ranges dedicated to different accounts removes an old dedication
Date Wed, 19 Jun 2013 11:37:19 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687891#comment-13687891
] 

ASF subversion and git services commented on CLOUDSTACK-3062:
-------------------------------------------------------------

Commit 4d02dbe6dfbd352bd35d2d981cfa7c7baff0fc8f in branch refs/heads/master-6-17-stable from
[~likithas]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4d02dbe ]

CLOUDSTACK-3062. Dedication of a guest vlan range that extends 2 ranges dedicated to different
accounts removes an old dedication

                
> 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: Likitha Shetty
>              Labels: integration-test
>             Fix For: 4.2.0
>
>
> 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. 

--
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

Mime
View raw message