Analyses:
1) As already commented, AMF responds to imm as soon as it sends quiesing 
assignment to active SU1. the SI to locked state, before receving removal 
response from amfnd.

 >> avd_sg_2n_si_admin_down: 'safSi=SI1,safApp=test2nApp', 0
Dec 18 14:07:30.268311 osafamfd [19840:siass.cc:0593] >> avd_susi_mod_send: SI 
'safSi=SI1,safApp=test2nApp', SU 'safSu=SU1,safSg=SG,safApp=test2nApp' 
ha_state:4

Dec 18 14:07:30.271254 osafamfd [19840:sg_2n_fsm.cc:3946] << 
avd_sg_2n_si_admin_down: 1
Dec 18 14:07:30.271261 osafamfd [19840:imm.cc:1713] >> 
avd_saImmOiAdminOperationResult: inv:373662154753, res:1
Dec 18 14:07:30.271269 osafamfd [19840:lga_api.c:0738] >> saLogWriteLogAsync
Dec 18 14:07:30.271276 osafamfd [19840:lga_mds.c:1168] >> lga_mds_msg_async_send


2)Also admin state of SI state is updated  before receving removal response 
from amfnd.

Dec 18 14:07:31.057731 osafamfd [19840:sg_2n_fsm.cc:2294] >> 
avd_sg_2n_susi_sucss_si_oper: 'safSu=SU1,safSg=SG,safApp=test2nApp', act:5, 
state:3
Dec 18 14:07:31.057743 osafamfd [19840:siass.cc:0634] >> avd_susi_del_send: SI 
'safSi=SI1,safApp=test2nApp', SU 'safSu=SU1,safSg=SG,safApp=test2nApp'
Dec 18 14:07:31.057757 osafamfd [19840:util.cc:0766] >> avd_snd_susi_msg
Dec 18 14:07:31.057766 osafamfd [19840:util.cc:1002] TR Sending 15 to 2030f
Dec 18 14:07:31.057773 osafamfd [19840:mbcsv_api.c:0773] >> mbcsv_process_sn

Here it sets the admin state:
Dec 18 14:07:31.058682 osafamfd [19840:si.cc:1368] >> avd_si_admin_state_set: 
safSi=SI1,safApp=test2nApp AdmState SHUTTING_DOWN => LOCKED

Now delete in other SU2:
Dec 18 14:07:31.064659 osafamfd [19840:siass.cc:0634] >> avd_susi_del_send: SI 
'safSi=SI1,safApp=test2nApp', SU 'safSu=SU2,safSg=SG,safApp=test2nApp'
Dec 18 14:07:31.064671 osafamfd [19840:


So before removal of assignments, SI becomes locked though SG FSM is still 
unstable.
So an application/admin will see TRY_AGAIN since SG is unstable for admin 
operation on the SG,SU or any related entity of this SG/APP.

Marking this ticket as duplicate of #505.



---

** [tickets:#670] SI state is moved to locked, before assignments are removed.**

**Status:** duplicate
**Created:** Wed Dec 18, 2013 08:48 AM UTC by surender khetavath
**Last Updated:** Thu Dec 26, 2013 06:35 AM UTC
**Owner:** Praveen

changeset : 4733
model : 2n
configuration : 1App,1SG,2SUs with 4comps each, 4SIs with 1 CSI each
si-si deps configured as SI1 sponsor for SI2,3,4 resp
SU1 is active, SU2 is standby.
SU1 is mapped to pl-3 and SU2 to pl-4
saAmfSGAutoRepair=1(True)
SuFailover=1(True)


Test:
1. shutdown the SI1 ( sponsor)
2. time out in CSI RemoveCbk


SI admin state is moved to LOCKED even before the assignments are cleared. 


states:
safSi=SI1,safApp=test2nApp
        saAmfSIAdminState=LOCKED(2)
        saAmfSIAssignmentState=UNASSIGNED(1)
safSi=SI2,safApp=test2nApp
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=FULLY_ASSIGNED(2)
safSi=SI3,safApp=test2nApp
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=FULLY_ASSIGNED(2)
safSi=SI4,safApp=test2nApp
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=FULLY_ASSIGNED(2)


/var/log/messages on PL-3:
Dec 18 14:07:27 PL-3 sshd[3787]: Accepted keyboard-interactive/pam for root 
from 192.168.56.105 port 55575 ssh2
Dec 18 14:07:29 PL-3 osafamfnd[3491]: NO Assigning 'safSi=SI1,safApp=test2nApp' 
QUIESCING to 'safSu=SU1,safSg=SG,safApp=test2nApp'
Dec 18 14:07:29 PL-3 osafamfnd[3491]: NO Assigned 'safSi=SI1,safApp=test2nApp' 
QUIESCING to 'safSu=SU1,safSg=SG,safApp=test2nApp'
Dec 18 14:07:40 PL-3 osafamfnd[3491]: NO saAmfSUFailover is true for 
'safSu=SU1,safSg=SG,safApp=test2nApp'
Dec 18 14:07:40 PL-3 osafamfnd[3491]: NO 
'safComp=COMP1,safSu=SU1,safSg=SG,safApp=test2nApp' faulted due to 
'csiRemovecallbackTimeout' : Recovery is 'suFailover'
Dec 18 14:07:40 PL-3 osafamfnd[3491]: NO Terminating components of 
'safSu=SU1,safSg=SG,safApp=test2nApp'(abruptly & unordered)
Dec 18 14:07:40 PL-3 osafamfnd[3491]: NO 'safSu=SU1,safSg=SG,safApp=test2nApp' 
Presence State INSTANTIATED => TERMINATING



---

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.
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to