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

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

GitHub user nitin-maharana reopened a pull request:

    https://github.com/apache/cloudstack/pull/1771

    CLOUDSTACK-9611: Dedicating a Guest VLAN range to Project does not work.

    Description:
    =========
    
    Trying to dedicate a guest VLAN range to an account fails. Either API 
documentation is wrong or code path needs to be corrected. 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 the 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".
    
    
![image](https://cloud.githubusercontent.com/assets/12583725/20559763/15fe55d8-b19c-11e6-9996-62602d269f10.png)
    
    
![image](https://cloud.githubusercontent.com/assets/12583725/20559765/1957af36-b19c-11e6-938f-e9c7c9eee987.png)
    
    Expected:
    =======
    The VLAN range should get dedicated to the project account.
    
    
![image](https://cloud.githubusercontent.com/assets/12583725/20559787/33ef67b2-b19c-11e6-90fd-41c9c583efd9.png)
    
    
![image](https://cloud.githubusercontent.com/assets/12583725/20559789/376cae22-b19c-11e6-9755-ff1e7237fb21.png)
    
    Resolution:
    ========
    Changed the account field of API to optional.
    Even if the account name is passed while adding from a particular project 
view, then it is ignored in API.
    
    Notes:
    =====
    If we do the dedication from default view then it works fine as no 
projectId is associated over there.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/nitin-maharana/CloudStack-Nitin nitin3

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1771.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1771
    
----
commit f56961392662f4b45e3e4cb989203f918ec19916
Author: Nitin Kumar Maharana <nitinkumar.mahar...@accelerite.com>
Date:   2017-02-28T10:57:38Z

    CLOUDSTACK-9611: Dedicating a Guest VLAN range to Project does not work.

----


> 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