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

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

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

CLOUDSTACK-3911: [PortableIP] there is no check while adding a zone
public range to see whether the same VLAN exists in portable IP range.

added check to enusre a VLAN id used for a public IP range is not used
for portable ip range


> [PortableIP] there is no check while adding a zone  public range to see 
> whether the same VLAN exists in portable IP range.
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3911
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3911
>             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
>         Environment: commit # ca474d0e09f772cb22abf2802a308a2da5351592
>            Reporter: venkata swamybabu budumuru
>            Assignee: Murali Reddy
>            Priority: Critical
>             Fix For: 4.2.1
>
>
> Steps to reproduce:
> 1. Have at least one portable IP range added
> for ex: VLAN 54, start ip : 10.147.54.100, end ip : 10.147.54.150, netmask : 
> 255.255.255.0
> 2. create an advanced zone. during the creation of advanced zone specify the 
> above VLAN with either the same of different ip ranges.
> Observations:
> (i) zone gets created successfully without any issues.
> (ii) Ideally it should throw an error saying there is another VLAN exists on 
> the network.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to