cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9500) VR configuration not clean properly after Public IP release
Date Fri, 09 Dec 2016 18:02:58 GMT


ASF GitHub Bot commented on CLOUDSTACK-9500:

Github user swill commented on the issue:
    The merge conflict between this PR and #1741 is a bit tricky, so I have included this
fix in #1741.  @vilisseranen and I are currently running both PRs in production so we had
to resolve the merge conflict for our deployment.  Since the resolution is not trivial, I
thought it made sense to just include this fix in my PR.

> VR configuration not clean properly after Public IP release
> -----------------------------------------------------------
>                 Key: CLOUDSTACK-9500
>                 URL:
>             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

View raw message