cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9500) VR configuration not clean properly after Public IP release
Date Fri, 21 Oct 2016 05:01:05 GMT

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

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

Github user blueorangutan commented on the issue:

    https://github.com/apache/cloudstack/pull/1706
  
    @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make
progress.


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

Mime
View raw message