[
https://issues.apache.org/jira/browse/CLOUDSTACK-9756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837296#comment-15837296
]
ASF GitHub Bot commented on CLOUDSTACK-9756:
--------------------------------------------
GitHub user jayapalu opened a pull request:
https://github.com/apache/cloudstack/pull/1917
CLOUDSTACK-9756: Configure to ignore the ipassoc failure
On failure of ip assoc in back end (In VR), added config option to ignore
or not to ignore failure. Using this failures won't be ignored and ip address
will not set to free in DB.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Accelerite/cloudstack RvRipRel
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1917.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1917
----
commit 66b0033cc9456dd875425387f92169dbdec005bf
Author: Jayapal <jayapal.ur...@accelerite.com>
Date: 2017-01-24T09:53:17Z
CLOUDSTACK-9756: Configure to ignore the ipassoc failure
----
> IP address must not be allocated to other VR if releasing ip address is
> failed
> -------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9756
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9756
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Reporter: Jayapal Reddy
> Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> Apply rule (delete) is success on failure of ip assoc on back end. Cloudstack
> ignored the ip assoc failure.
> Due to this the ip got freed and assigned to another network/account. It
> caused the ip to be present in more than one router.
> Fix: Failing the apply rule (delete) on ipassoc failure
> Repro steps:
> 1. Configure PF/static nat/Firewall rules
> 2. Delete the rule configured.
> On deleting the rule, fail the ip assoc on the router.
> 3. Delete rule fails because ip assoc got failed.
> For RVR:
> 1. acquire several public ips,
> 2. add some rules on those public ips, so ips should show up in RVR,
> 3. change ipassoc.sh in RVR, make it always returns error on disassociate ip.
> 4. disassociate ip from UI, ip should is freed even though disassociate
> fails inside VR.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
