Analysis:
1) During shutdown operation on SU1 quiescing assignments are given honoring SI
dependency.
Status of counter after receiving quiescing response from all SIs from SU1
hosted amfnd:
TR safSu=SU1,safSg=SG,safApp=test2nApp saAmfSUNumCurrActiveSIs=0
TR safSi=SI1,safApp=test2nApp saAmfSINumCurrActiveAssignments=0 similar for
SI2-SI4.
2)After this AMF initiated failover of SU1 giving active assignment for sponsor
SI1 in SU2.
status of counters:
TR safSu=SU2,safSg=SG,safApp=test2nApp saAmfSUNumCurrActiveSIs=1
TR safSu=SU2,safSg=SG,safApp=test2nApp saAmfSUNumCurrStandbySIs=3
TR safSi=SI1,safApp=test2nApp saAmfSINumCurrActiveAssignments=1
<------------------here it becomes 1.
TR safSi=SI1,safApp=test2nApp saAmfSINumCurrStandbyAssignments=0
So active counter for SI1 is increased by 1.
3) This assignment was rejected and led to sufailover as recovery. AMFD sent
delete to SU1.
For deletion counters are updated after receiving response from amfnd.
At the same time, as a part of sufailover escalation SUSIs of SU2 are
deleted in which counters are updated as
TR safSi=SI2,safApp=test2nApp saAmfSINumCurrStandbyAssignments=0
TR safSi=SI3,safApp=test2nApp saAmfSINumCurrStandbyAssignments=0
TR safSi=SI4,safApp=test2nApp saAmfSINumCurrStandbyAssignments=0
Here counter for SI1 was not updated because its SUSI was in Modify state.In
AMF the relevent code is in siass.cc in avd_susi_delete()
if (susi->fsm == AVD_SU_SI_STATE_MODIFY) {
/* Dont delete here, if i am in modify state.
only happens when active -> qsd and standby rebooted
*/
} else if ((susi->fsm == AVD_SU_SI_STATE_ASGND) || (susi->fsm
== AVD_SU_SI_STATE_ASGN)){
if (SA_AMF_HA_STANDBY == susi->state) {
4) After this when deletion response for SU1 comes, AMF deletes SUSIs in SU1
without affecting the
counters in SIs.
Since all SUSIs are deleted in SU1 and SU2, all assignment counters should
be 0 for SIs and SUs.
Since in 2) assignment counter for active was increased for SI1, it is not zero.
5) Now when SU2 was repaired and instantiated, AMFD freshely assigned the
sponsor SI1 and again increased the active counter by 1
safSi=SI1,safApp=test2nApp saAmfSINumCurrActiveAssignments=2
This is the reason, AMF is showing partially assigned status for Si1.
Since from functionality perspective all things are working fine, priority of
the issue
can be reduced to minor.
---
** [tickets:#666] one si shows partially assigned though assignments are
proper**
**Status:** unassigned
**Created:** Tue Dec 17, 2013 12:34 PM UTC by surender khetavath
**Last Updated:** Tue Dec 17, 2013 04:07 PM UTC
**Owner:** nobody
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 case:
1. shutdown the active SU1
2. SI1 rejects the new active assignment ie. assignment to SU2
3. unlock of SU1
After the unlock of SU
/var/log/messages on pl-4:
Dec 17 17:50:23 PL-4 osafamfnd[22050]: NO Assigning
'safSi=SI1,safApp=test2nApp' ACTIVE to 'safSu=SU2,safSg=SG,safApp=test2nApp'
Dec 17 17:50:23 PL-4 osafamfnd[22050]: NO saAmfSUFailover is true for
'safSu=SU2,safSg=SG,safApp=test2nApp'
Dec 17 17:50:23 PL-4 osafamfnd[22050]: NO
'safComp=COMP1,safSu=SU2,safSg=SG,safApp=test2nApp' faulted due to
'csiSetcallbackFailed' : Recovery is 'suFailover'
Dec 17 17:50:23 PL-4 osafamfnd[22050]: NO Terminating components of
'safSu=SU2,safSg=SG,safApp=test2nApp'(abruptly & unordered)
Dec 17 17:50:23 PL-4 osafamfnd[22050]: NO 'safSu=SU2,safSg=SG,safApp=test2nApp'
Presence State INSTANTIATED => TERMINATING
Dec 17 17:50:23 PL-4 logger: CLC-CLI spawnd cleanup for
safComp=COMP1,safSu=SU2,safSg=SG,safApp=test2nApp
Dec 17 17:50:23 PL-4 logger: CLC-CLI spawnd cleanup for
safComp=COMP2,safSu=SU2,safSg=SG,safApp=test2nApp
Dec 17 17:50:23 PL-4 logger: CLC-CLI spawnd cleanup for
safComp=COMP4,safSu=SU2,safSg=SG,safApp=test2nApp
Dec 17 17:50:23 PL-4 logger: CLC-CLI spawnd cleanup for
safComp=COMP3,safSu=SU2,safSg=SG,safApp=test2nApp
Dec 17 17:50:23 PL-4 osafamfnd[22050]: NO 'safSu=SU2,safSg=SG,safApp=test2nApp'
Presence State TERMINATING => UNINSTANTIATED
Dec 17 17:50:23 PL-4 osafamfnd[22050]: NO Terminated all components in
'safSu=SU2,safSg=SG,safApp=test2nApp'
Dec 17 17:50:23 PL-4 osafamfnd[22050]: NO Informing director of sufailover
Dec 17 17:50:23 PL-4 osafamfnd[22050]: NO 'safSu=SU2,safSg=SG,safApp=test2nApp'
Presence State UNINSTANTIATED => UNINSTANTIATED
states:
safSi=SI1,safApp=test2nApp
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3) <----Here
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)
safSu=SU1,safSg=SG,safApp=test2nApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSu=SU2,safSg=SG,safApp=test2nApp
saAmfSUAdminState=UNLOCKED(1)
saAmfSUOperState=ENABLED(1)
saAmfSUPresenceState=INSTANTIATED(3)
saAmfSUReadinessState=IN-SERVICE(2)
safSISU=safSu=SU2\,safSg=SG\,safApp=test2nApp,safSi=SI2,safApp=test2nApp
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=SG\,safApp=test2nApp,safSi=SI3,safApp=test2nApp
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=SG\,safApp=test2nApp,safSi=SI1,safApp=test2nApp
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=SG\,safApp=test2nApp,safSi=SI4,safApp=test2nApp
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI1,safApp=test2nApp
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI3,safApp=test2nApp
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI4,safApp=test2nApp
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=SG\,safApp=test2nApp,safSi=SI2,safApp=test2nApp
saAmfSISUHAState=ACTIVE(1)
---
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
