cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9611) Dedicating a Guest VLAN range to Project does not work
Date Tue, 28 Feb 2017 17:29:45 GMT


ASF GitHub Bot commented on CLOUDSTACK-9611:

Github user nitin-maharana commented on the issue:
    @ustcweizhou @koushik-das : I implemented the way @ustcweizhou's suggested. It was purely
an UI change. But I found an issue while testing.
    On API side, the entire logic uses VLAN owner account details, they find it from the account
given by the user. So, they made account field as mandatory. But that contradicts when it
is accessed from a project view(This issue). 
    The current logic works in a default view because we don't add projectid details while
accessing the API. But when it is accessed from a particular project view, by default the
projectid parameter is added with the API call, So this issue arises. 
    Now, if we go with the change suggested by @ustcweizhou, once we select the scope as domain,
we don't pass any account details, so the logic can't able to find the owner hence gives an
    According to my suggestion, On API side, we should make the account field as optional
and on UI front, we should make it mandatory and the account field will appear only in case
of default view, which will fix the issue. Please give your input on this. Accordingly, I
will proceed.
    Please see the current change(I pushed it here)

> Dedicating a Guest VLAN range to Project does not work
> ------------------------------------------------------
>                 Key: CLOUDSTACK-9611
>                 URL:
>             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

View raw message