[jira] [Commented] (CLOUDSTACK-4045) IP address acquired with associateIpAddress is marked as source NAT, causing disassociateIpAddress to fail later

["John Burwell (JIRA)" <ji...@apache.org>]

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

John Burwell commented on CLOUDSTACK-4045:
------------------------------------------

[~muralireddy] is this still a bug in 4.9?  If so, I would like it to add to backlog to address as part of LTS.

> IP address acquired with associateIpAddress is marked as source NAT, causing disassociateIpAddress to fail later
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4045
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4045
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.0.0, 4.0.1, 4.0.2, 4.1.0, 4.1.1, 4.2.0
>            Reporter: Murali Reddy
>            Assignee: Murali Reddy
>             Fix For: Future
>
>
> When you can create network, network is in allocated state. when network is implemented CloudStack implicitly should acquire a public IP for source nat. But there is assumption that first IP this is associated with network is always for source NAT IP. So when you do
> 1. create network (network is in allocated state)
> 2. acquire a public IP and associate with the network
> 3. disassociate ip address
> #3 will fail because CloudStack marks the IP acquired in #1 to be source NAT. For users this is counter-intutive because when a IP is acquired, he/she should be able to release it as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)