ASF GitHub Bot commented on CLOUDSTACK-4045:

houthuis opened a new pull request #2382: CLOUDSTACK-4045 IP address acquired 
with associateIpAddress is marked as source NAT
URL: https://github.com/apache/cloudstack/pull/2382
   added a check for network state when determining whether a new IP should be 
source NAT. this prevents associated IP's to be marked as source NAT when the 
network is in allocated state, causing disassociateIpAddress to fail later
   Code will now throw a InvalidParameterValueException in the above scenario.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> 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
>            Priority: Major
>             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

Reply via email to