cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "shweta agarwal (JIRA)" <>
Subject [jira] [Reopened] (CLOUDSTACK-2989) normal user are allowed to create isolated network offerings with vlan assignments
Date Wed, 03 Jul 2013 06:56:20 GMT


shweta agarwal reopened CLOUDSTACK-2989:

Verified on 4.2 stable branch on build number :

CloudPlatform-4.2-138-rhel6.3 . Bug still exists .
> normal user are allowed to create isolated network offerings with vlan assignments
> ----------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-2989
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller, UI
>    Affects Versions: 4.2.0
>         Environment: build:
> CloudStack-non-OSS-MASTER-472-rhel6.3
>            Reporter: shweta agarwal
>            Assignee: Mice Xia
>            Priority: Critical
>             Fix For: 4.2.0
> Repro steps:
> 1. Create a domain and an account within the domain
> 2. Create a network offerings with specify vlan=true  for isolated network 
> 3. Create network with network offering created in step 2 as a domain account created
in step 1
> Bug:
> Network creation is successful
> Expected result:
> normal user should not be allowed to create network with specify Vlan=true isolated network
> Even Functional spec  says:
> nly ROOT admin is aware of the Vlans in the system. So only he can create the Isolated
network with the vlan defined. UI should handle it and don't display network offerings with
"specifyVlan=true" when create a new Isolated network.
> Even  vial Normal user UI 
> Create network dialog shows Network offerings with specify vlan=ture and when I try to
create a network offerings it passes also
> So that means both at UI level and api level this condition is not checked

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