cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daan Hoogland (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CLOUDSTACK-4045) IP address acquired with associateIpAddress is marked as source NAT, causing disassociateIpAddress to fail later
Date Fri, 12 Jan 2018 11:37:00 GMT

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

Daan Hoogland reassigned CLOUDSTACK-4045:
-----------------------------------------

    Assignee: Henko Holtzhausen  (was: Murali Reddy)

> 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: Henko Holtzhausen
>             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.4.14#64029)

Mime
View raw message