[jira] [Commented] (CLOUDSTACK-9500) VR configuration not clean properly after Public IP release

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824578#comment-15824578 ] 

ASF GitHub Bot commented on CLOUDSTACK-9500:
--------------------------------------------

Github user swill commented on the issue:

    https://github.com/apache/cloudstack/pull/1706
  
    We have proven that the fix in this PR does not work.  I have removed it from #1741.
    
    A new PR which we have proven does work is at: #1907


> 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)