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 Wed, 12 Oct 2016 19:39:20 GMT

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

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

Github user pdion891 commented on the issue:

    https://github.com/apache/cloudstack/pull/1706
  
    Hi @remibergsma,  
    
    We found this issue CLOUDSTACK-9500 where Public IP's is not removed from a VR when the
Public IP is release. this cause routing issues because the arp table is refresh at any operation
on the VR which reset de MAC for the release IP that can be used into another VR in a VPC
deployement model. 
    
    Is this something you faced? 
    
    Thanks,


> 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