Not observing this issue on changeset:   4546:902b3c7ea830.

Steps performed to reproduce it (configuration is in 313.tgz): 
1)amf-adm lock safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1
2)immcfg -a saAmfNodeSuFailoverMax=0 safAmfNode=SC-2,safAmfCluster=myAmfCluster
3)immcfg -a saAmfNodeSuFailoverMax=0 safAmfNode=SC-1,safAmfCluster=myAmfCluster
4)amf-adm lock safSu=SU1,safSg=AmfDemo,safApp=AmfDemo1
error - command timed out (alarm)

As active controller goes down SC-2 becomes active.
When SC-1 rejoins and perform unlock of SU1 and Su2. All SIs show proper 
assignments/states.

Attached 313.tgz contains configuration and AMF traces.

Please reopen this ticket if again observed and also attach logs. 


---

** [tickets:#313] Wrong HA state reported after node-failover**

**Status:** worksforme
**Created:** Fri May 24, 2013 08:33 AM UTC by Nagendra Kumar
**Last Updated:** Tue Oct 15, 2013 12:37 PM UTC
**Owner:** Praveen

Migrated from http://devel.opensaf.org/ticket/3043

When running with 
1) set saAmfNodeSuFailoverMax=0 for all nodes.
2) And in application SG set saAmfSgtDefSuRestartMax=0.


In a 2 controller system I repeatedly killed a Locked app (all other instances 
where also locked so there was no where to failover to) until the required 
number of component-restarts occurred and eventually opensaf escalated to 
node-failure.


When querying IMM on the other node after the failover occurred (and the 
original node restarted) the si HA state of the failed instance is 'quiesced' 
instead of 'standby.


$ immlist $(amf-find siass | grep FaultM)
Name Type Value(s)
========================================================================
safSISU SA_NAME_T safSISU=safSu=1\,safSg=FaultManager?\,safApp=FaultManager? 
(56) 
saAmfSISUHAState SA_UINT32_T 2 (0x2)
saAmfSISUHAReadinessState SA_UINT32_T 1 (0x1)
SaImmAttrImplementerName? SA_STRING_T safAmfService 
SaImmAttrClassName? SA_STRING_T SaAmfSIAssignment 
SaImmAttrAdminOwnerName? SA_STRING_T <Empty>


Name Type Value(s)
========================================================================
safSISU SA_NAME_T safSISU=safSu=2\,safSg=FaultManager?\,safApp=FaultManager? 
(56) 
saAmfSISUHAState SA_UINT32_T 3 (0x3)
saAmfSISUHAReadinessState SA_UINT32_T 1 (0x1)
SaImmAttrImplementerName? SA_STRING_T safAmfService 
SaImmAttrClassName? SA_STRING_T SaAmfSIAssignment 
SaImmAttrAdminOwnerName? SA_STRING_T <Empty>





---

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.
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to