[
https://issues.apache.org/jira/browse/CLOUDSTACK-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15671280#comment-15671280
]
ASF GitHub Bot commented on CLOUDSTACK-9500:
--------------------------------------------
Github user remibergsma commented on the issue:
https://github.com/apache/cloudstack/pull/1706
@pdion891 Sorry for being late to the party. We've seen this issue too and
resolved it in a different way. Removing the ip from the databag probably won't
work too well, as it is used to deprovision the old ip address from the router.
This is what works well for us instead:
https://github.com/MissionCriticalCloud/cosmic/pull/114/files
> 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)
