[
https://issues.apache.org/jira/browse/CLOUDSTACK-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeev N closed CLOUDSTACK-3911.
---------------------------------
Verified on the latest build from 4.2 branch with commit id
f9731144cda4d7982cc4be1e60c1e4aa3b3ca2e2. Now with the fix we can't use the
same vlan for portable ip and public ip.
> [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)
