cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-2984) admin able to assign vlan within Physical Network Vnet range
Date Tue, 02 Jul 2013 17:19:20 GMT


ASF subversion and git services commented on CLOUDSTACK-2984:

Commit 12e984f869a487a1370be652b0cfc3bbe687d9b7 in branch refs/heads/master-6-17-stable from
[;h=12e984f ]

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:
>             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:

View raw message