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-4069) [EIP/ELB] [UI] There is no option to acquire IP address for non-ROOT domain users.
Date Thu, 08 Aug 2013 23:27:48 GMT


ASF subversion and git services commented on CLOUDSTACK-4069:

Commit 9c5b293fe093cbed885de6f1a5f6352aca164959 in branch refs/heads/master from [~jessicawang]
[;h=9c5b293 ]

CLOUDSTACK-4069: listNetworkOfferings API has been changed to not return system-owned network
offerings to regular user(domain user). Therefore, change UI to determine whether a network
is EIP/ELB upon listNetworks API response instead of listNetworkOfferings API response.

> [EIP/ELB] [UI] There is no option to acquire IP address for non-ROOT domain users. 
> -----------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-4069
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.2.0
>         Environment: commit id # 7522f811672f66bc0cc13a33f4f3737ef03f22af
>            Reporter: venkata swamybabu budumuru
>            Assignee: Jessica Wang
>            Priority: Critical
>             Fix For: 4.2.0
>         Attachments: jessica_computer__using_venkata_databaseDump.jpg, logs.tgz, Screen
Shot 2013-08-05 at 2.12.20 PM.png
> Steps to reproduce:
> 1. Have latest cloudstack setup with at least one EIP/ELB enabled zone
> 2. Login as non-ROOT domain user
> 3. Go to Network -> View IP Address and check for option to "Acquire IP address"
> Observations:
> (i) There is no option like "Acquire IP Address" button in the UI.
> (ii) API is working fine without any issues.
> Attaching the screenshot of the same along with logs and db dump.

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