[
https://issues.apache.org/jira/browse/CLOUDSTACK-2984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698011#comment-13698011
]
ASF subversion and git services commented on CLOUDSTACK-2984:
-------------------------------------------------------------
Commit 724be3f5f79253a98628929e4e74412a2e76a383 in branch refs/heads/4.2 from
[~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=724be3f ]
CLOUDSTACK-2984: createNetwork call - when vlan is specified, check that its
not coming from the physical network vnet range as this range is used for
dynamic vlan allocation during the network implementation stage
> admin able to assign vlan within Physical Network Vnet range
> ------------------------------------------------------------
>
> Key: CLOUDSTACK-2984
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2984
> 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: build:
> CloudStack-non-OSS-MASTER-472-rhel6.3
> Reporter: shweta agarwal
> Assignee: Alena Prokharchyk
> Fix For: 4.2.0
>
>
> Repro steps:
> 1. Setup a zone
> 2.Create a network offerings with specify vlan=true for isolated network
> 3. Use this network offerings to create a isolated network and provide a vlan
> id as the one within Physical Network Vnet range
> Bug:
> Step 3 succeeded and network is created with the specified vlan
> Expected result:
> It should report error that The VLAN tag is already being used for the guest
> network in zone
> In case of shared network if we try to use Vlan id that belongs to a zone we
> gets proper error message
--
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
