- **status**: review --> fixed
- **Comment**:
[staging:da9b03]
[staging:50285c]
[staging:b8dfd4]
[staging:5f9ef2]
[staging:09c46a]
[staging:59a26a]
[staging:f19978]
[staging:314f5c]
[staging:c74278]
[staging:7d8b8a]
[staging:1c48dd]
[staging:1c0e18]
changeset: 5954:da9b031be19f
branch: opensaf-4.3.x
parent: 5948:32afdc0a8169
user: Mathivanan N.P.<[email protected]>
date: Wed Oct 01 20:40:30 2014 -0400
summary: clm: avoid stale node down processing and unexpected track
callback [#1120]
changeset: 5955:50285c825a40
branch: opensaf-4.3.x
user: Mathivanan N.P.<[email protected]>
date: Wed Oct 01 20:42:10 2014 -0400
summary: clm: during failover, process agent down before node downs [#1120]
changeset: 5956:b8dfd4a2cc01
branch: opensaf-4.3.x
user: Mathivanan N.P.<[email protected]>
date: Wed Oct 01 20:51:30 2014 -0400
summary: clm: do not send stale track to the node that rebooted and
cameback [#1120]
changeset: 5957:5f9ef2b113af
branch: opensaf-4.4.x
parent: 5949:85358c92df21
user: Mathivanan N.P.<[email protected]>
date: Wed Oct 01 20:40:30 2014 -0400
summary: clm: avoid stale node down processing and unexpected track
callback [#1120]
changeset: 5958:09c46a76306e
branch: opensaf-4.4.x
user: Mathivanan N.P.<[email protected]>
date: Wed Oct 01 20:42:10 2014 -0400
summary: clm: during failover, process agent down before node downs [#1120]
changeset: 5959:59a26ad0410f
branch: opensaf-4.4.x
user: Mathivanan N.P.<[email protected]>
date: Wed Oct 01 20:51:30 2014 -0400
summary: clm: do not send stale track to the node that rebooted and
cameback [#1120]
changeset: 5960:f1997847065c
branch: opensaf-4.5.x
parent: 5952:f9e12d446db6
user: Mathivanan N.P.<[email protected]>
date: Wed Oct 01 20:40:30 2014 -0400
summary: clm: avoid stale node down processing and unexpected track
callback [#1120]
changeset: 5961:314f5c10a738
branch: opensaf-4.5.x
user: Mathivanan N.P.<[email protected]>
date: Wed Oct 01 20:42:10 2014 -0400
summary: clm: during failover, process agent down before node downs [#1120]
changeset: 5962:c7427848a172
branch: opensaf-4.5.x
user: Mathivanan N.P.<[email protected]>
date: Wed Oct 01 20:51:30 2014 -0400
summary: clm: do not send stale track to the node that rebooted and
cameback [#1120]
changeset: 5963:7d8b8a405454
parent: 5953:6ba1f54cd42f
user: Mathivanan N.P.<[email protected]>
date: Wed Oct 01 20:40:30 2014 -0400
summary: clm: avoid stale node down processing and unexpected track
callback [#1120]
changeset: 5964:1c48dd418efb
user: Mathivanan N.P.<[email protected]>
date: Wed Oct 01 20:42:10 2014 -0400
summary: clm: during failover, process agent down before node downs [#1120]
changeset: 5965:1c0e1876ef7b
tag: tip
user: Mathivanan N.P.<[email protected]>
date: Wed Oct 01 20:51:30 2014 -0400
summary: clm: do not send stale track to the node that rebooted and
cameback [#1120]
---
** [tickets:#1120] CLM: clm sends SA_CLM_NODE_LEFT to active node **
**Status:** fixed
**Milestone:** 4.5.0
**Created:** Fri Sep 19, 2014 12:02 PM UTC by hano
**Last Updated:** Thu Sep 25, 2014 01:47 PM UTC
**Owner:** Mathi Naickan
clm sends SA_CLM_NODE_LEFT to active node which is wrong. This message is then
received by the amfnd function clm_node_left which do terminate components.
This should be changed to node reboot instead.
The real problem is why clm sends a SA_CLM_NODE_LEFT to an active node.
It seems related to when a node leaves the cluster, the active clmd sends a
checkpoint update of node down to the standby clmd.
If that checkpoint reaches the standby before the MDS event for the same event,
then the cleanup of the node_down_list will fail, this problem is under
investigation. A "quick" patch will be sent out to avoid this fault.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
