[
https://issues.apache.org/jira/browse/CLOUDSTACK-9015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010573#comment-15010573
]
ASF GitHub Bot commented on CLOUDSTACK-9015:
--------------------------------------------
Github user wilderrodrigues commented on the pull request:
https://github.com/apache/cloudstack/pull/1070#issuecomment-157655322
Although it’s based on an assumption, enforced by good pattern recognition,
what happened to @miguelaferreira and @remibergsma was:
1. the code does “delete_nat_rules()” and tries to SSH (expected failure).
that works fine
2. The code does “add_nat_rules()” and tries to SSH again, which should
pass - and did all the times I tried, and I’m not lying
so, what’s the problem then?
the “delete_nat_rule()” method is deleting the nat_rule, as it says, but
not deleting the public IP that was acquired. So, when the code calls the
“add_nat_rule()” method, it acquires a new IP and adds a nat rule to that IP.
what does it mean? that you guys got a situation where the test tried to
SSH via the IP that doesn’t contain a NAT (PF) rule. that explain the ssh error.
I fixed it, but first need to test before pushing.
Cheers,
Wilder
> Redundant VPC Virtual Router's state is BACKUP & BACKUP or MASTER & MASTER
> --------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9015
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9015
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.6.0
> Environment: CloudStack master(2015/10/31) 4.6.0-snapshot
> Hypervisor CentOS6/KVM
> SystemVM
> build #654 (2015/10/22 19:27:55)
> http://jenkins.buildacloud.org/job/build-systemvm64-master/lastSuccessfulBuild/artifact/tools/appliance/dist/systemvm64template-master-4.6.0-kvm.qcow2.bz2
> Reporter: satoru nakaya
> Assignee: Wilder Rodrigues
> Priority: Critical
> Fix For: 4.6.1
>
>
> Steps of reproduce.
> 1)Create VPC (Redundant VPC offering)
> 2)Create tier
> 3)Create VM Instance on this tier
> 4)Check Redundant state (good)
> r-14-VM Redundant state:MASTER
> r-15-VM Redundant state:BACKUP
> 5) Reboot Router r-14-VM
> 6)Check Redundant state (good)
> r-14-VM Redundant state:BACKUP
> r-15-VM Redundant state:MASTER
> 7) Reboot Router r-15-VM
> 8)Check Redundant state (bad)
> r-14-VM Redundant state:BACKUP
> r-15-VM Redundant state:BACKUP
> 9)Check Log(r-14-VM's /var/log/messages)
> Nov 1 00:46:29 r-14-VM Keepalived_vrrp[3711]: VRRP_Instance(inside_network)
> sending 0 priority
> Nov 1 00:47:34 r-14-VM Keepalived_vrrp[2179]: Netlink: filter function error
> Nov 1 00:47:34 r-14-VM Keepalived_healthcheckers[2178]: Netlink: filter
> function error
> Nov 1 00:47:53 r-14-VM Keepalived_healthcheckers[2178]: Netlink: filter
> function error
> Nov 1 00:47:53 r-14-VM Keepalived_vrrp[2179]: Netlink: filter function error
> Nov 1 00:47:54 r-14-VM Keepalived_healthcheckers[2178]: Netlink: filter
> function error
> Nov 1 00:47:54 r-14-VM Keepalived_vrrp[2179]: Netlink: filter function error
> 10)Check Log(r-15-VM's /var/log/messages)
> Nov 1 00:49:19 r-15-VM Keepalived_vrrp[3682]: VRRP_Instance(inside_network)
> sending 0 priority
> Nov 1 00:50:25 r-15-VM Keepalived_vrrp[2179]: Netlink: filter function error
> Nov 1 00:50:25 r-15-VM Keepalived_healthcheckers[2178]: Netlink: filter
> function error
> Nov 1 00:50:45 r-15-VM Keepalived_healthcheckers[2178]: Netlink: filter
> function error
> Nov 1 00:50:45 r-15-VM Keepalived_vrrp[2179]: Netlink: filter function error
> Nov 1 00:50:45 r-15-VM Keepalived_healthcheckers[2178]: Netlink: filter
> function error
> Nov 1 00:50:45 r-15-VM Keepalived_vrrp[2179]: Netlink: filter function error
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
