You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ilya musayev (JIRA)" <ji...@apache.org> on 2014/06/06 19:32:03 UTC
[jira] [Commented] (CLOUDSTACK-3911) [PortableIP] there is no check
while adding a zone public range to see whether the same VLAN exists in
portable IP range.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14020103#comment-14020103 ]
ilya musayev commented on CLOUDSTACK-3911:
------------------------------------------
Hi Guys
Why was this implemented? It should be administrators responsibility to make sure he does proper VLAN tracking.
Perhaps we can change this to warning message instead?
There are cases when you deploy cloudstack in 1 VLAN range and you need to place all Networks on the same VLAN range.
This fix forces me to use 2 VLAN ranges. Please provide context for this fix.
Thanks
ilya
> [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.2#6252)