[
https://issues.apache.org/jira/browse/CLOUDSTACK-9500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15650128#comment-15650128
]
ASF GitHub Bot commented on CLOUDSTACK-9500:
--------------------------------------------
Github user murali-reddy commented on the issue:
https://github.com/apache/cloudstack/pull/1706
@jburwell #1659 has a fix which complements this patch.Basically when first
IP is associated with an interface routing table is created and should be
deleted when last IP associated is removed. #1659 handles that case.
@vilisseranen could you please see if there is regression. Looks like IP
may be getting removed from ips.json data bag, but not really getting
dis-associated from the interface. Failure in below tests indicate so.
test_network_rules_acquired_public_ip_3_Load_Balancer_Rule Failure 36.36
test_network.py
test_network_rules_acquired_public_ip_2_nat_rule Failure 31.31
test_network.py
est_network_rules_acquired_public_ip_1_static_nat_rule Failure 93.29
test_network.py
> 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)
