- **status**: review --> fixed
- **Version**: 4.4 --> 4.5
- **Milestone**: future --> 4.5.0
---
** [tickets:#1060] AMF: reset of cluster startup timer does not happen (#76)**
**Status:** fixed
**Milestone:** 4.5.0
**Created:** Wed Sep 10, 2014 10:18 AM UTC by Hans Feldt
**Last Updated:** Tue Sep 23, 2014 05:12 AM UTC
**Owner:** Nagendra Kumar
When all SUs are ENABLED and INSTANTIATED it was intended in #76 that
assignments should be done and not wait for the cluster start timeout. This
does not work. It is not a problem since once the timer expires assignments
happen but it waste time in testing...
Analysis:
The trigger is the state change from DISABLED to ENABLED, in sgproc.cc and the
call to cluster_su_instantiation_done()
cluster_su_instantiation_done() checks the SUs presence state for INSTANTIATED.
Since that is not yet updated if returns False. When the SU goes to
INSTANTIATED, no new check is done.
Logs:
15 12:03:00 09/10/2014 NO safApp=safAmfService "Starting cluster
startup timer"
16 12:03:01 09/10/2014 NO safApp=safAmfService
"safSu=PL-4,safSg=NoRed,safApp=OpenSAF PresenceState INSTANTIATING =>
INSTANTIATED"
17 12:03:01 09/10/2014 NO safApp=safAmfService
"safSu=PL-4,safSg=NoRed,safApp=OpenSAF OperState DISABLED => ENABLED"
18 12:03:01 09/10/2014 NO safApp=safAmfService
"safSu=PL-4,safSg=NoRed,safApp=OpenSAF ReadinessState OUT_OF_SERVICE =>
IN_SERVICE"
19 12:03:01 09/10/2014 NO safApp=safAmfService
"safSi=NoRed1,safApp=OpenSAF assigned to safSu=PL-4,safSg=NoRed,safApp=OpenSAF
HA State 'ACTIVE'"
20 12:03:01 09/10/2014 NO safApp=safAmfService
"safSu=PL-5,safSg=NoRed,safApp=OpenSAF PresenceState INSTANTIATING =>
INSTANTIATED"
21 12:03:02 09/10/2014 NO safApp=safAmfService
"safSu=PL-5,safSg=NoRed,safApp=OpenSAF OperState DISABLED => ENABLED"
22 12:03:02 09/10/2014 NO safApp=safAmfService
"safSu=PL-5,safSg=NoRed,safApp=OpenSAF ReadinessState OUT_OF_SERVICE =>
IN_SERVICE"
23 12:03:02 09/10/2014 NO safApp=safAmfService
"safSu=PL-3,safSg=NoRed,safApp=OpenSAF PresenceState INSTANTIATING =>
INSTANTIATED"
24 12:03:02 09/10/2014 NO safApp=safAmfService
"safSu=PL-3,safSg=NoRed,safApp=OpenSAF OperState DISABLED => ENABLED"
25 12:03:02 09/10/2014 NO safApp=safAmfService
"safSu=PL-3,safSg=NoRed,safApp=OpenSAF ReadinessState OUT_OF_SERVICE =>
IN_SERVICE"
26 12:03:02 09/10/2014 NO safApp=safAmfService
"safSi=NoRed3,safApp=OpenSAF assigned to safSu=PL-5,safSg=NoRed,safApp=OpenSAF
HA State 'ACTIVE'"
27 12:03:02 09/10/2014 NO safApp=safAmfService
"safSi=NoRed5,safApp=OpenSAF assigned to safSu=PL-3,safSg=NoRed,safApp=OpenSAF
HA State 'ACTIVE'"
28 12:03:02 09/10/2014 NO safApp=safAmfService
"safAmfNode=PL-4,safAmfCluster=myAmfCluster OperState DISABLED => ENABLED"
29 12:03:02 09/10/2014 NO safApp=safAmfService
"safSu=2,safSg=1,safApp=osaftest OperState DISABLED => ENABLED"
30 12:03:02 09/10/2014 NO safApp=safAmfService
"safAmfNode=PL-5,safAmfCluster=myAmfCluster OperState DISABLED => ENABLED"
31 12:03:02 09/10/2014 NO safApp=safAmfService
"safAmfNode=PL-3,safAmfCluster=myAmfCluster OperState DISABLED => ENABLED"
32 12:03:02 09/10/2014 NO safApp=safAmfService
"safSu=1,safSg=1,safApp=osaftest OperState DISABLED => ENABLED"
33 12:03:03 09/10/2014 NO safApp=safAmfService
"safSu=SC-2,safSg=NoRed,safApp=OpenSAF PresenceState INSTANTIATING =>
INSTANTIATED"
34 12:03:03 09/10/2014 NO safApp=safAmfService
"safSu=SC-2,safSg=NoRed,safApp=OpenSAF OperState DISABLED => ENABLED"
35 12:03:03 09/10/2014 NO safApp=safAmfService
"safSu=SC-2,safSg=NoRed,safApp=OpenSAF ReadinessState OUT_OF_SERVICE =>
IN_SERVICE"
36 12:03:03 09/10/2014 NO safApp=safAmfService
"safSi=NoRed4,safApp=OpenSAF assigned to safSu=SC-2,safSg=NoRed,safApp=OpenSAF
HA State 'ACTIVE'"
37 12:03:03 09/10/2014 NO safApp=safAmfService
"safSu=SC-2,safSg=2N,safApp=OpenSAF PresenceState INSTANTIATING => INSTANTIATED"
38 12:03:03 09/10/2014 NO safApp=safAmfService
"safSu=SC-2,safSg=2N,safApp=OpenSAF OperState DISABLED => ENABLED"
39 12:03:03 09/10/2014 NO safApp=safAmfService
"safSu=SC-2,safSg=2N,safApp=OpenSAF ReadinessState OUT_OF_SERVICE => IN_SERVICE"
40 12:03:03 09/10/2014 NO safApp=safAmfService
"safSi=SC-2N,safApp=OpenSAF assigned to safSu=SC-2,safSg=2N,safApp=OpenSAF HA
State 'STANDBY'"
41 12:03:03 09/10/2014 NO safApp=safAmfService
"safAmfNode=SC-2,safAmfCluster=myAmfCluster OperState DISABLED => ENABLED"
42 12:03:05 09/10/2014 NO safApp=safAmfService
"safSu=1,safSg=1,safApp=osaftest PresenceState INSTANTIATING => INSTANTIATED"
43 12:03:05 09/10/2014 NO safApp=safAmfService
"safSu=1,safSg=1,safApp=osaftest ReadinessState OUT_OF_SERVICE => IN_SERVICE"
44 12:03:05 09/10/2014 NO safApp=safAmfService
"safSu=2,safSg=1,safApp=osaftest PresenceState INSTANTIATING => INSTANTIATED"
>>>> Here the last SU is ENABLED and INSTANTIATED but nothing happens...
45 12:03:05 09/10/2014 NO safApp=safAmfService
"safSu=2,safSg=1,safApp=osaftest ReadinessState OUT_OF_SERVICE => IN_SERVICE"
46 12:03:10 09/10/2014 NO safApp=safAmfService "Cold sync complete of
2020f"
47 12:03:10 09/10/2014 NO safApp=safAmfService "Cold sync complete at
2020f"
>>>> until here when the timeout happens
48 12:03:30 09/10/2014 NO safApp=safAmfService "Cluster startup
timeout, assigning SIs to SUs"
---
Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets