[jira] [Updated] (CLOUDSTACK-9189) rVPC ACL doesn't recover after cleaning up through the NetworkGarbageCollector

["Wilder Rodrigues (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-9189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wilder Rodrigues updated CLOUDSTACK-9189:
-----------------------------------------
    Affects Version/s:     (was: 4.6.2)
                           (was: 4.6.1)
                           (was: 4.6.0)

> rVPC ACL doesn't recover after cleaning up through the NetworkGarbageCollector
> ------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9189
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9189
>             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
>            Reporter: Wilder Rodrigues
>            Assignee: Wilder Rodrigues
>            Priority: Critical
>             Fix For: 4.7.1
>
>
> In order to reproduce this bug quicker is better to change the network.gc.interval and gc.wait from 600 seconds to 10 seconds via Global Settings and restart your management server.
> - deploy a rVPC
> - deploy VM in it
> - make port forwarding (2nd ip, firewall and such)
> - confirm it works
> - stop the vm
> - after some time (20 seconds * 3 - approximately) the network garbage collector will come and tear down the network since there are no more VMs
> - all the nics will be fine and the guest nic will be gone. The routers should be on BACKUP/BACKUP
> - then start the vm again
> - the nics get plugged again and keepalived will decide on a new master.
> - try to SSH into the VM via the public IP. It will fail
> The only way to get it working afain is:
> - Replace the network ACL - for example, default allow all
> - Try to SSH again and it works fine
> - Replace back to your original ACL
> - Try to SSH again and it works fine



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)