Reproduced with following patch in amf_demo.c:

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
@@ -123,6 +123,7 @@ static void amf_csi_set_callback(SaInvoc
        switch (ha_state) {
        case SA_AMF_HA_ACTIVE:
                status = foo_activate();
+               sleep (1);
                break;
        case SA_AMF_HA_STANDBY:
                /*
@@ -139,6 +140,13 @@ static void amf_csi_set_callback(SaInvoc
                break;
        case SA_AMF_HA_QUIESCING:
                /* the effect of admin op lock on SU or node or ... */
+
+               if (0 != 
strcmp(my_comp_name.value,"safComp=AmfDemo,safSu=SU2,safSg=AmfDemo,safApp=AmfDemo1"))
+               {
+                       sleep (1);
+               }
+
+
                status = 0;
                break;
        default:
@@ -160,7 +168,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 sg


---

** [tickets:#492] Assignments are not removed during SG shutdown with faulty 
component**

**Status:** unassigned
**Created:** Tue Jul 09, 2013 07:32 AM UTC by surender khetavath
**Last Updated:** Mon Jul 29, 2013 04:48 AM UTC
**Owner:** Praveen

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
SU1 was active and SU2 standby
si-si deps configured as SI1<-SI2<-SI3<-SI4


Test:
Shutdown of SG. A component in active SU is made to reply with FAILED_OP in 
quiescing cbk. sg goes to locked state but assignments are not removed. 
Later unlock of SG fails with time-out

SU states:
safSu=SU2,safSg=SGONE,safApp=TWONAPP
        saAmfSUAdminState=UNLOCKED(1)
        saAmfSUOperState=ENABLED(1)
        saAmfSUPresenceState=INSTANTIATED(3)
        saAmfSUReadinessState=OUT-OF-SERVICE(1)
safSu=SU1,safSg=SGONE,safApp=TWONAPP
        saAmfSUAdminState=UNLOCKED(1)
        saAmfSUOperState=DISABLED(2)
        saAmfSUPresenceState=TERMINATING(4)
        saAmfSUReadinessState=OUT-OF-SERVICE(1)
safSu=SU3,safSg=SGONE,safApp=TWONAPP
        saAmfSUAdminState=UNLOCKED(1)
        saAmfSUOperState=ENABLED(1)
        saAmfSUPresenceState=INSTANTIATED(3)
        saAmfSUReadinessState=OUT-OF-SERVICE(1)
safSu=SU4,safSg=SGONE,safApp=TWONAPP
        saAmfSUAdminState=UNLOCKED(1)
        saAmfSUOperState=ENABLED(1)
        saAmfSUPresenceState=INSTANTIATED(3)
        saAmfSUReadinessState=OUT-OF-SERVICE(1)
safSu=SU5,safSg=SGONE,safApp=TWONAPP
        saAmfSUAdminState=UNLOCKED(1)
        saAmfSUOperState=ENABLED(1)
        saAmfSUPresenceState=UNINSTANTIATED(1)
        saAmfSUReadinessState=OUT-OF-SERVICE(1)

sg state:
safSg=SGONE,safApp=TWONAPP
        saAmfSGAdminState=LOCKED(2)

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

syslog on active ctrl ie sc-1:
Jul  9 12:43:09 SC-1 osafamfd[3725]: WA SG not in STABLE state 
(safSg=SGONE,safApp=TWONAPP)
Jul  9 12:43:10 SC-1 osafamfd[3725]: WA SG not in STABLE state 
(safSg=SGONE,safApp=TWONAPP)
Jul  9 12:43:11 SC-1 osafamfd[3725]: WA SG not in STABLE state 
(safSg=SGONE,safApp=TWONAPP)
Jul  9 12:43:12 SC-1 osafamfd[3725]: WA SG not in STABLE state 
(safSg=SGONE,safApp=TWONAPP)
Jul  9 12:43:13 SC-1 osafamfd[3725]: WA SG not in STABLE state 
(safSg=SGONE,safApp=TWONAPP)



---

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.
------------------------------------------------------------------------------
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
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to