This happens during SI lock also. In both the cases SG remain in SI_OPER FSM 
state, so most probably this issue is same as #1485. In #1485 also SU stucks in 
TERMINATING state during component failover when SG is in SI_OPER state. 


---

** [tickets:#1515] AMF : SU struck in terminating for failure during csi 
assignment in si-swap (Nway)**

**Status:** unassigned
**Milestone:** 4.5.2
**Created:** Mon Oct 05, 2015 12:45 PM UTC by Srikanth R
**Last Updated:** Tue Oct 06, 2015 05:37 AM UTC
**Owner:** nobody


Changeset : 6901 
amf application :  3 SUs with 5 SIs. ( Su1 and SU3 hosted on PL-3 and SU2 
hosted on PL-4). 
                              Nway redundancy model.
                              
Issue :  SU struck in terminating for failure during csi active assignment  in 
si-swap (Nway)      

Steps :

 -> Initially brought up the application by unlocking the SG and below are the 
assignments .
 
 ****************************************************************************
             TestApp_SI1     TestApp_SI2     TestApp_SI3     TestApp_SI4     
TestApp_SI5   
****************************************************************************
TestApp_SU1    ACTIVE         ACTIVE         ACTIVE         STANDBY             
        
TestApp_SU2    STANDBY         STANDBY         STANDBY                         
ACTIVE     
TestApp_SU3                                                    ACTIVE         
STANDBY     
****************************************************************************

 -> Before performing si-swap operation on SU1, ensured that component with SI1 
standby assignment shall reject the active callback
 
 
 -> Invoked the si-swap operation. As the component responded with 
ERR_FAILED_OP in active callback, recovery action is triggered for SU.  
 
 
 Oct  5 15:15:02 PAYLOAD-2 osafamfnd[2659]: NO Assigning 
'safSi=TestApp_SI1,safApp=TestApp_Nway' ACTIVE to 
'safSu=TestApp_SU2,safSg=TestApp_SG1,safApp=TestApp_Nwa
 Oct  5 15:15:02 PAYLOAD-2 osafamfnd[2659]: NO 
'safComp=COMP1,safSu=TestApp_SU2,safSg=TestApp_SG1,safApp=TestApp_Nway' faulted 
due to 'csiSetcallbackFailed' : Recovery is 'componentFailover'
Oct  5 15:15:02 PAYLOAD-2 osafamfnd[2659]: NO 
'safSu=TestApp_SU2,safSg=TestApp_SG1,safApp=TestApp_Nway' Presence State 
INSTANTIATED => TERMINATING


But the SU struck in terminating state and below are the final assignments.



****************************************************************************
             TestApp_SI1     TestApp_SI2     TestApp_SI3     TestApp_SI4     
TestApp_SI5   
****************************************************************************
TestApp_SU1    QUIESCED         ACTIVE         ACTIVE         STANDBY         
STANDBY     
TestApp_SU2    ACTIVE         STANDBY         STANDBY                         
QUIESCED     
TestApp_SU3    STANDBY                                         ACTIVE         
ACTIVE     
****************************************************************************

                              
                              






---

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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to