Analysis:

1) Admin lock of si:
   Sep  9 15:19:13.004740 osafamfd [2844:si.cc:0780] >> si_admin_op_cb: 
safSi=TWONSI1,safApp=TWONAPP op=2
   Sep  9 15:19:13.004755 osafamfd [2844:si.cc:1361] >> set_admin_state: 
safSi=TWONSI1,safApp=TWONAPP AdmState UNLOCKED =>    

 LOCKED

 - quiesced state to SI4 for this si
   Sep  9 15:19:13.006099 osafamfd [2844:siass.cc:0517] >> avd_susi_mod_send: 
SI 'safSi=TWONSI1,safApp=TWONAPP', SU    

'safSu=SU4,safSg=SGONE,safApp=TWONAPP' ha_state:3
 -removal to SU3
   Sep  9 15:19:13.012606 osafamfd [2844:siass.cc:0558] >> avd_susi_del_send: 
SI 'safSi=TWONSI1,safApp=TWONAPP', SU      

'safSu=SU3,safSg=SGONE,safApp=TWONAPP'

2) AMFD recevies quiesced response from SU4
   Sep  9 15:19:13.233946 osafamfd [2844:sgproc.cc:0751] >> 
avd_su_si_assign_evh: id:72, node:2040f, act:5,   

'safSu=SU4,safSg=SGONE,safApp=TWONAPP', 'safSi=TWONSI1,safApp=TWONAPP', ha:3, 
err:1, single:0

   -and it sends delete to SU4 for SI:
    Sep  9 15:19:13.236862 osafamfd [2844:siass.cc:0558] >> avd_susi_del_send: 
SI 'safSi=TWONSI1,safApp=TWONAPP', SU    

'safSu=SU4,safSg=SGONE,safApp=TWONAPP'


3) Even though fault occurs SU3 components, AMFD recevies deletion success for 
standby state from SU3:
   Sep  9 15:19:13.706567 osafamfd [2844:sgproc.cc:0751] >> 
avd_su_si_assign_evh: id:122, node:2030f, act:4,   

'safSu=SU3,safSg=SGONE,safApp=TWONAPP', 'safSi=TWONSI1,safApp=TWONAPP', ha:2, 
err:1, single:0
  
   and it deletes its SUSIs

4)AMFD receives su-failover request from AMFND for SU3:
  Sep  9 15:19:13.739681 osafamfd [2844:sgproc.cc:0468] >> 
avd_su_oper_state_evh: id:126, node:2030f,  

'safSu=SU3,safSg=SGONE,safApp=TWONAPP' state:2
 
  -SUSIs are deleted for SU3:
    Sep  9 15:19:13.751336 osafamfd [2844:su.cc:1871] >> delete_all_susis: 
'safSu=SU3,safSg=SGONE,safApp=TWONAPP'
  - AMFD initiates instantiation of SU2
  
5) Fault occurs in SU4, but AMFD gets susi success for removal of assignment
   Sep  9 15:19:14.198934 osafamfd [2844:sgproc.cc:0751] >> 
avd_su_si_assign_evh: id:78, node:2040f, act:4,   

'safSu=SU4,safSg=SGONE,safApp=TWONAPP', 'safSi=TWONSI1,safApp=TWONAPP', ha:3, 
err:1, single:0

   -AMFD updates SI dep states:
     Sep  9 15:19:14.202627 osafamfd [2844:si_dep.cc:0202] TR 
'safSi=TWONSI2,safApp=TWONAPP' si_dep_state ASSIGNED =>      

READY_TO_UNASSIGN
   -AMFD creates new standby assignment for SI2-SI5 in SU1
    
    
6)AMFD receives su-failover request from AMFND hosting SU4:
  - AMFND sends deletes for newly created SUSIs of SI2 and SI5 in SU1
    Sep  9 15:19:14.378466 osafamfd [2844:siass.cc:0558] >> avd_susi_del_send: 
SI 'safSi=TWONSI2,safApp=TWONAPP', SU    

'safSu=SU1,safSg=SGONE,safApp=TWONAPP'
    Sep  9 15:19:14.385644 osafamfd [2844:siass.cc:0558] >> avd_susi_del_send: 
SI 'safSi=TWONSI5,safApp=TWONAPP', SU    

'safSu=SU1,safSg=SGONE,safApp=TWONAPP'
    Sep  9 15:19:14.388733 osafamfd [2844:siass.cc:0558] >> avd_susi_del_send: 
SI 'safSi=TWONSI5,safApp=TWONAPP', SU    

'safSu=SU4,safSg=SGONE,safApp=TWONAPP'

    SUSIs are deleted in SU4

7)AMFD receives SUSI success response
   -For standby assignment in SU1
   Sep  9 15:19:14.429159 osafamfd [2844:sgproc.cc:0751] >> 
avd_su_si_assign_evh: id:184, node:2010f, act:2,      

'safSu=SU1,safSg=SGONE,safApp=TWONAPP', 'safSi=TWONSI2,safApp=TWONAPP', ha:2, 
err:1, single:0
   Sep  9 15:19:14.541944 osafamfd [2844:sgproc.cc:0751] >> 
avd_su_si_assign_evh: id:185, node:2010f, act:2,   

'safSu=SU1,safSg=SGONE,safApp=TWONAPP', 'safSi=TWONSI3,safApp=TWONAPP', ha:2, 
err:1, single:0
   Sep  9 15:19:14.647197 osafamfd [2844:sgproc.cc:0751] >> 
avd_su_si_assign_evh: id:186, node:2010f, act:2,    

'safSu=SU1,safSg=SGONE,safApp=TWONAPP', 'safSi=TWONSI4,safApp=TWONAPP', ha:2, 
err:1, single:0
   Sep  9 15:19:14.737268 osafamfd [2844:sgproc.cc:0751] >> 
avd_su_si_assign_evh: id:187, node:2010f, act:2,    

'safSu=SU1,safSg=SGONE,safApp=TWONAPP', 'safSi=TWONSI5,safApp=TWONAPP', ha:2, 
err:1, single:0

  -Removal response 
   Sep  9 15:19:14.869077 osafamfd [2844:sgproc.cc:0751] >> 
avd_su_si_assign_evh: id:188, node:2010f, act:4,    

'safSu=SU1,safSg=SGONE,safApp=TWONAPP', 'safSi=TWONSI2,safApp=TWONAPP', ha:2, 
err:1, single:0
   Sep  9 15:19:14.975149 osafamfd [2844:sgproc.cc:0751] >> 
avd_su_si_assign_evh: id:189, node:2010f, act:4,   
   'safSu=SU1,safSg=SGONE,safApp=TWONAPP', 'safSi=TWONSI5,safApp=TWONAPP', 
ha:2, err:1, single:0
 
  -AMFD updates si_dep states:
    Sep  9 15:19:14.976291 osafamfd [2844:si_dep.cc:0202] TR 
'safSi=TWONSI2,safApp=TWONAPP' si_dep_state READY_TO_UNASSIGN => 

   SPONSOR_UNASSIGNED
   Sep  9 15:19:14.977062 osafamfd [2844:si_dep.cc:0202] TR 
'safSi=TWONSI3,safApp=TWONAPP' si_dep_state READY_TO_UNASSIGN =>  

  SPONSOR_UNASSIGNED

   -Creation of SUSI for SI5 in SU1
   Sep  9 15:19:14.977398 osafamfd [2844:sgproc.cc:0070] >> avd_new_assgn_susi: 
'safSu=SU1,safSg=SGONE,safApp=TWONAPP'    
   'safSi=TWONSI5,safApp=TWONAPP' state=1

8)AMFD gets SUSI success response for SI5
  Sep  9 15:19:15.100167 osafamfd [2844:sgproc.cc:0751] >> 
avd_su_si_assign_evh: id:190, node:2010f, act:2, 

'safSu=SU1,safSg=SGONE,safApp=TWONAPP', 'safSi=TWONSI5,safApp=TWONAPP', ha:1, 
err:1, single:0


Here also susi success before su-fialover request creates standby assignments 
for dependents. This will not happen if AMFD receives direclty su-failover 
request, it will delete the  SUSIs and no new SUSIs for dependents will be 
created as the sponsor is locked.



---

** [tickets:#1055] dependent si assignments are not removed**

**Status:** unassigned
**Milestone:** 4.3.3
**Created:** Tue Sep 09, 2014 09:59 AM UTC by surender khetavath
**Last Updated:** Tue Sep 09, 2014 10:00 AM UTC
**Owner:** nobody

changeset : 5697
model : 2n
configuration : 1App,1SG,5SUs with 3comps each, 5SIs with 3CSIs each
si-si deps configured as SI1<-SI2<-SI3<-SI4.
SU1 is active, SU2 is standby.
SU1 is mapped to SC-1 and SU2 to SC-2,SU3 to PL-3 and SU4,5 to PL-4
saAmfSGAutoRepair=1(True)
SuFailover=1(True)

Test:
lock sponsor si
when remove cbk is received, report error on self through errorReport api

SI1 is seen in locked state but the dependent assignments are not removed.


safSi=TWONSI1,safApp=TWONAPP
        saAmfSIAdminState=LOCKED(2)
        saAmfSIAssignmentState=UNASSIGNED(1)
safSi=TWONSI2,safApp=TWONAPP
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=UNASSIGNED(1)
safSi=TWONSI3,safApp=TWONAPP
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
safSi=TWONSI5,safApp=TWONAPP
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
safSi=TWONSI4,safApp=TWONAPP
        saAmfSIAdminState=UNLOCKED(1)
        saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)

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

safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI5,safApp=TWONAPP
        saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI4,safApp=TWONAPP
        saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU1\,safSg=SGONE\,safApp=TWONAPP,safSi=TWONSI3,safApp=TWONAPP
        saAmfSISUHAState=STANDBY(2)




---

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.
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to