You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sean Lair (JIRA)" <ji...@apache.org> on 2017/09/12 14:35:00 UTC
[jira] [Resolved] (CLOUDSTACK-9872) Batch S2S VPN script doesn't
return all responses
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Lair resolved CLOUDSTACK-9872.
-----------------------------------
Resolution: Fixed
> Batch S2S VPN script doesn't return all responses
> -------------------------------------------------
>
> Key: CLOUDSTACK-9872
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9872
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Virtual Router
> Affects Versions: 4.8.0, 4.9.0, 4.10.0.0, 4.8.1.1, 4.9.0.1
> Environment: Any using Site-to-Site VPNs. Seems to be all versions of Cloudstack
> Reporter: Sean Lair
> Priority: Minor
> Fix For: 4.9.3.0
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> The checkbatchs2svpn.sh VR script returns ("via echo") that status of each requested S2S VPN check one-at-a-time. If there is even a slight delay between VPN checks, the sshExecutor stops monitoring stdout and assumes it has all of the output.
> When checking the management server logs, we see a request to check X number of VPNs, but the response is occasionally less than X number... The rest of the Cloudstack code assumes "isConnected" as false if the VPN is not included in the response.
> We've noticed that if an account had more than 3 site-to-site VPNs, that there are many errors per day stating that a S2S VPN is down.
> This is exacerbated by Issue CLOUDSTACK-9873, because that issues causes the S2S VPN check (and many others) to run twice as often as intended.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)