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

ASF GitHub Bot commented on CLOUDSTACK-9611:
--------------------------------------------

Github user nitin-maharana commented on the issue:

    https://github.com/apache/cloudstack/pull/1771
  
    @ustcweizhou : Passing project with domain won't create any issue but not 
passing any account details when we call the API from default view creates an 
issue. Because the internal logic expects account owner of VLAN when dedicated 
from the default view. In the case of project view, it gets the account detail 
from selected project.


> Dedicating a Guest VLAN range to Project does not work
> ------------------------------------------------------
>
>                 Key: CLOUDSTACK-9611
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9611
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Nitin Kumar Maharana
>
> Trying to dedicate a guest VLAN range to an account fails. If we pass both 
> account and projectid parameters to the dedicateGuestVlanRange (which are not 
> mentioned as mutually exclusive in API description) the API layer throws 
> error saying both are mutually exclusive.
> Steps to Reproduce:
> ================
> Create an account. Create a project in that account.
> Go to admin account and change view to the above project.
> Navigate to Infrastructure -> Zone -> Physical Network -> Guest -> Dedicate 
> Guest VLAN range.
> Try to dedicate the guest VLAN range from the project view for the account 
> associated with the project.
> It fails with Error saying accountName and projectId are mutually exclusive.
> Expected:
> ========
> The VLAN range should get dedicated to the project account.
> Notes:
> =====
> If we do the dedication from default view then it works fine as no projectid 
> is associated over there.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to