Attached configuration (AppConfig-2N_2Comp_2SI_2CSI.xml_491_5sis_1) can be used 
to reproduce the issue.
AppConfig-2N.xml is extended to prepare the configuration.
Besides this one change in amf_demo.c is required for reproducing it.
Here is the patch for amf_demo.c in default branch:


diff --git a/samples/amf/sa_aware/amf_demo.c b/samples/amf/sa_aware/amf_demo.c
--- a/samples/amf/sa_aware/amf_demo.c
+++ b/samples/amf/sa_aware/amf_demo.c
@@ -138,6 +138,11 @@ static void amf_csi_set_callback(SaInvoc
                status = foo_deactivate();
                break;
        case SA_AMF_HA_QUIESCING:
+               if (0 == 
strcmp(my_comp_name.value,"safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1"))
 {
+                       sleep (.001);
+               }
+
+
                /* the effect of admin op lock on SU or node or ... */
                status = 0;
                break;
@@ -160,7 +165,7 @@ static void amf_csi_set_callback(SaInvoc

        if (ha_state == SA_AMF_HA_QUIESCING) {
                /* "gracefully quiescing CSI work assignment" */
-               sleep(1);
+               sleep(11);
                rc = saAmfCSIQuiescingComplete(my_amf_hdl, invocation, 
SA_AIS_OK);
                if (rc != SA_AIS_OK) {
                        syslog(LOG_ERR, "saAmfCSIQuiescingComplete FAILED - 
%u", rc);




steps to reproduce:

1) Bring attached application up.
2) Ensure that SU2 is active on SC-2 ( SC-2 is standby) and above patch is 
included in component code.
3) shutdown operation on SU2




Attachment: AppConfig-2N_2Comp_2SI_2CSI.xml_491_5sis_1 (22.2 kB; text/plain) 


---

** [tickets:#491] Presence state of SU stuck in Terminating state after 
shutdown**

**Status:** unassigned
**Created:** Tue Jul 09, 2013 06:14 AM UTC by surender khetavath
**Last Updated:** Fri Jul 12, 2013 11:14 AM UTC
**Owner:** nobody

Changeset : 4325
Model : TWON
Configuration: 1SG,5SUs having 3comps each, 5SIs with 3Csis each.
Intially: 5Node cluster, SU1 mapped to SC-1,SU2 to SC-2,SU3-PL3,SU4&SU5 to PL-4
SU2 was active and SU3 standby
si-si deps configured as SI1<-SI2<-SI3<-SI4

Test:
Shutdown of SU2. A component in SU2 is made to reply with FAILED_OP in 
quiescing cbk. Comp_restart recovery triggered, escalating it to SU failover. 
SU3 became active, but assignments are still in QUiesced state for SU2.

State of SU : 
safSu=SU2,safSg=SGONE,safApp=TWONAPP
        saAmfSUAdminState=LOCKED(2)
        saAmfSUOperState=DISABLED(2)
        saAmfSUPresenceState=TERMINATING(4)
        saAmfSUReadinessState=OUT-OF-SERVICE(1)

SI states:
safSi=TWONSI2,safApp=TWONAPP
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
safSi=TWONSI3,safApp=TWONAPP
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
safSi=TWONSI5,safApp=TWONAPP
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
safSi=TWONSI1,safApp=TWONAPP
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
safSi=TWONSI4,safApp=TWONAPP
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)

SUSI assignments:
safSISU=safSu=SU3\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI5,safApp=TWONAPP
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU3\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI4,safApp=TWONAPP
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI1,safApp=TWONAPP
        saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
        saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SC-2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU3\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI2,safApp=TWONAPP
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU3\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI1,safApp=TWONAPP
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU3\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI3,safApp=TWONAPP
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI5,safApp=TWONAPP
        saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI4,safApp=TWONAPP
        saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=PL-3\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed4,safApp=OpenSAF
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=PL-4\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed3,safApp=OpenSAF
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=PL-5\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed5,safApp=OpenSAF
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI3,safApp=TWONAPP
        saAmfSISUHAState=QUIESCED(3)
safSISU=safSu=SU2\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI2,safApp=TWONAPP
        saAmfSISUHAState=QUIESCED(3)



---

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.
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to