[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Murali Reddy updated CLOUDSTACK-4111:
-------------------------------------

    Summary: [PortableIP][USABILITY] Prompt "Acquire New IP - Cross Zones - 
YES/NO" wizard only when there is portable IP range added at region level.  
(was: [PortableIP][UI] Prompt "Acquire New IP - Cross Zones - YES/NO" wizard 
only when there is portable IP range added at region level.)
    
> [PortableIP][USABILITY] Prompt "Acquire New IP - Cross Zones - YES/NO" wizard 
> only when there is portable IP range added at region level.
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4111
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4111
>             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 # 9cd4e089a5798f422961940efbf8ae33ed906b87
>            Reporter: venkata swamybabu budumuru
>            Assignee: Murali Reddy
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Steps to reproduce:
> 1. Have latest CloudStack setup with at least one advanced zone.
> 2. Create an isolated network and deploy at least 1 VM using this network.
> 3. Go to Netoworks -> View IP Address -> Acquire IP Address 
> Observations:
> (i)Though there is no portable IP range at region level added in the above 
> steps, it still prompts for "Cross zones" wizard.
> (ii) Enable the above wizard only when there is portable IP ranged exists in 
> the system.
> (iii) This means, when there is no portable ip range and when user tries to 
> acquire an ip then we should send isPortable=False as part of the 
> associateIpAddress API.

--
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: http://www.atlassian.com/software/jira

Reply via email to