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-9639) Unable to create shared network with vLan isolation
Date Fri, 23 Dec 2016 12:22:00 GMT

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

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

Commit c7b0345ed28e3173f485e4c1394784b350851666 in cloudstack's branch refs/heads/master from
[~rohit.yadav@shapeblue.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c7b0345 ]

Merge pull request #1804 from Accelerite/CLOUDSTACK-9639

CLOUDSTACK-9639: Unable to create shared network with vLan isolationDescription:
=========
Create shared network fails with Error.
While creating a shared network it fails to create with Error "The new IP range you have specified
has overlapped with the guest network in the zone: XYZ. Please specify a different gateway/netmask"

Steps to Reproduce:
===============
1. Create an isolated network with a subnet eg: 10.1.1.0/24
2. Create a shared network with the same subnet but different VLAN, we should observe this
issue.

Expected Behaviour:
===============
It shouldn't restrict the creation of the guest network with the same subnet as long as they
are segmented by VLAN.

ACTUAL BEHAVIOR:
===============
It doesn't allow the creation of shared guest networks if there is any isolated guest network
using the same subnet although it allows using the same subnet in multiple shared networks.

Cause:
=====
The issue is happening because, when Shared network is getting created we are checking if
there is any guest network already implemented with the same CIDR and throwing the error without
checking if they are having same VLAN also. Creating the same CIDR shared network with different
VLAN should be allowed.

Fix:
===
When creating a shared network, if there is any existing guest network with the same CIDR,
we check if they are having the same VLAN, if they are in same VLAN, then we don't allow creating
it. If they are in the same CIDR with different VLAN then we allowing to create the network.

* pr/1804:
  CLOUDSTACK-9639: Unable to create shared network with vLan isolation

Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>


> Unable to create shared network with vLan isolation
> ---------------------------------------------------
>
>                 Key: CLOUDSTACK-9639
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9639
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Nitin Kumar Maharana
>
> Create shared network fails with error While creating a shared network it fails to create
with Error "The new IP range you have specified has overlapped with the guest network in the
zone: XYZ. Please specify a different gateway/netmask"
> Steps to Reproduce:
> ===============
> Create an isolated network with a subnet eg: 10.1.1.0.24
> Create a shared network with the same subnet but different VLAN, we should observe this
issue.
> EXPECTED BEHAVIOR 
> ===================
> It shouldn't restrict the creation of guest network's with same subnet as long as they
are segmented by VLAN.
> ACTUAL BEHAVIOR 
> ================
> It doesn't allow the creation of shared guest networks if there is any isolated guest
network using the same subnet although it allows using the same subnet in multiple shared
networks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message