[
https://issues.apache.org/jira/browse/CLOUDSTACK-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15569659#comment-15569659
]
ASF GitHub Bot commented on CLOUDSTACK-9500:
--------------------------------------------
GitHub user vilisseranen opened a pull request:
https://github.com/apache/cloudstack/pull/1706
CLOUDSTACK-9500: remove the IP from the databag if it is not used
https://issues.apache.org/jira/browse/CLOUDSTACK-9500
This removes the IP from the databags ips.json and forwardingrules.json
when the IP is unused.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vilisseranen/cloudstack CLOUDSTACK-9500
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1706.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 #1706
----
commit b44e3be8c5295fc88c7f71aa42ec9214911092ed
Author: Clement Contini <[email protected]>
Date: 2016-09-19T18:16:59Z
remove the IP from the databag if it is not used
----
> VR configuration not clean properly after Public IP release
> -----------------------------------------------------------
>
> Key: CLOUDSTACK-9500
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9500
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Virtual Router
> Affects Versions: 4.7.0, 4.9.0
> Reporter: Pierre-Luc Dion
>
> On a VPC, releasing a public IP that had Port Forwarding does not remove
> configuration of the public IP on the VR configs
> ({{/etc/cloudstack/forwardingrules.json}}, {{/etc/cloudstack/ips.json}})
> So, when this IP is reassign to another VPC, it cause arp table issues on
> switches, because 2 MAC try to own this IP from 2 different VRs. the IP on
> the old VR is not pignable but the switches arp table get updated every time
> the previous VR have configuration changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
