You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/07/15 12:48:49 UTC

[jira] [Commented] (CLOUDSTACK-2960) [portableIPrange] CS should check the portable ip range, vlan with existing public ip ranges and vlans

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

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

Commit f53db88bae5c490d0d7bd9c7d6e7d47a3b293654 in branch refs/heads/master from [~murali.reddy]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f53db88 ]

CLOUDSTACK-2960: [portableIPrange] CS should check the portable ip range, vlan with
existing public ip ranges and vlans

adds a validation check to ensure there is no VLAN in the zones with
same id

                
> [portableIPrange] CS should check the portable ip range, vlan with existing public ip ranges and vlans 
> -------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2960
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2960
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.2.0
>         Environment: commit id # 673b293d75419a4b76379092db2b204cdc6160a4
>            Reporter: venkata swamybabu budumuru
>            Assignee: Murali Reddy
>             Fix For: 4.2.0
>
>
> Steps to reproduce :
> 1. Have latest cloudstack setup with at least one adv zone.
> 2. Have the following public ip range already added 
> start ip : 10.147.44.80
> end ip : 10.147.44.89
> gw : 10.147.44.1
> mask : 255.255.255.0
> VLAN : 44
> 3. Add the same above range including vlan to the portable ip range
> Observations:
> (i) This goes fine without any issues.
> (ii) Allowing the above will create issue when user tries to have the same ip from public ip range and portable ip range on the same router.
> Attaching all the required logs and db dump to the bug.

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