GitHub user yvsubhash opened a pull request:
https://github.com/apache/cloudstack/pull/1761
CLOUDSTACK-9592 Empty responses from site to site connection status aâ¦
CLOUDSTACK-9592 Empty responses from site to site connection status are not
handled propertly
vpn connection status gives responses like the below sometimes
Processing: { Ans: , MgmtId: 7203499016310, via: 1(10.147.28.37), Ver: v1,
Flags: 110,
[{"com.cloud.agent.api.CheckS2SVpnConnectionsAnswer":{"ipToConnected":{},"ipToDetail":{},"details":"","result":true,"wait":0}}]
}
2016-09-27 08:52:19,211 DEBUG [c.c.a.t.Request]
(RouterStatusMonitor-1:ctx-c20f391d) (logid:c217239d) Seq
1-2315413158421863581: Received: { Ans: , MgmtId: 7203499016310, via:
1(10.147.28.37), Ver: v1, Flags: 110,
{ CheckS2SVpnConnectionsAnswer }
In the above scenario, the bug in the processing of this response assumes
the connection is disconnected even though it is not disconnected and there
would be two consecutive alerts in logs as well as emails even though there is
not actual disconnection and reconnection
Site-to-site Vpn Connection XYZ-VPN on router r-197-VM(id: 197) just switch
from Disconnected to Connected
Site-to-site Vpn Connection to D1 site to site VPN on router r-372-VM(id:
372) just switch from Connected to Disconnected
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yvsubhash/cloudstack CLOUDSTACK-9592
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1761.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1761
----
commit 6c8bab5fe30a1c1adacb9b73afe89c41f00cad17
Author: subhash yedugundla <[email protected]>
Date: 2016-06-24T09:36:48Z
CLOUDSTACK-9592 Empty responses from site to site connection status are not
handled propertly
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
