cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "rashmidixit (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9500) VR configuration not clean properly after Public IP release
Date Mon, 16 Jan 2017 20:55:26 GMT


rashmidixit commented on CLOUDSTACK-9500:

Github user swill commented on the issue:
    @vilisseranen can you close this PR?

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

> 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