1)AMF sends reboot message to the SU1 which it hosts:
Apr 16 16:14:34.194896 osafamfd [2791:avd_util.c:1719] TR Sending REBOOT MSG to
2010f
Apr 16 16:14:34.194906 osafamfd [2791:avd_sgproc.c:0500] <<
avd_su_oper_state_evh
After sending the message active AMF still processes:
Apr 16 16:14:34.200130 osafamfd [2791:avd_sgproc.c:0542] >>
avd_su_si_assign_evh: id:115, node:2020f, act:5,
'safSu=SU2,safSg=SGONE,safApp=TWONAPP', 'safSi=TWONSI3,safApp=TWONAPP', ha:3,
err:1, single:0
and sends quiesced to:
Apr 16 16:14:34.200918 osafamfd [2791:avd_siass.c:0599] >> avd_susi_mod_send:
SI 'safSi=TWONSI2,safApp=TWONAPP', SU 'safSu=SU2,safSg=SGONE,safApp=TWONAPP'
ha_state:3
2)SC-2 becomes active at:
Apr 16 16:14:41.276021 osafamfd [3370:avd_role.c:0072] >> avd_role_change_evh:
cause=1, role=1
Apr 16 16:14:41.276039 osafamfd [3370:avd_role.c:0251] >> avd_role_failover
Apr 16 16:14:41.282322 osafamfd [3370:avd_role.c:0252] NO FAILOVER StandBy -->
Active
Apr 16 16:14:41.282347 osafamfd [3370:mbcsv_api.c:0662] >>
mbcsv_process_chg_role_request: Change HA role for the
3)SC-2 performs deletion of susis:
Apr 16 16:14:41.346545 osafamfd [3370:avd_siass.c:0433] >> avd_susi_delete:
safSu=SU1,safSg=SGONE,safApp=TWONAPP safSi=TWONSI1,safApp=TWONAPP
Apr 16 16:14:41.346648 osafamfd [3370:avd_siass.c:0433] >> avd_susi_delete:
safSu=SU1,safSg=SGONE,safApp=TWONAPP safSi=TWONSI2,safApp=TWONAPP
Apr 16 16:14:41.346655 osafamfd [3370:avd_siass.c:0504] << avd_susi_delete
Apr 16 16:14:41.346821 osafamfd [3370:avd_siass.c:0433] >> avd_susi_delete:
safSu=SU1,safSg=SGONE,safApp=TWONAPP safSi=TWONSI3,safApp=TWONAPP
Apr 16 16:14:41.346834 osafamfd [3370:avd_siass.c:0504] << avd_susi_delete
Apr 16 16:14:41.347024 osafamfd [3370:avd_siass.c:0433] >> avd_susi_delete:
safSu=SU1,safSg=SGONE,safApp=TWONAPP safSi=TWONSI4,safApp=TWONAPP
Apr 16 16:14:41.347032 osafamfd [3370:avd_siass.c:0504] << avd_susi_delete
Apr 16 16:14:41.347125 osafamfd [3370:avd_siass.c:0433] >> avd_susi_delete:
safSu=SU1,safSg=SGONE,safApp=TWONAPP safSi=TWONSI5,safApp=TWONAPP
Apr 16 16:14:41.347131 osafamfd [3370:avd_siass.c:0504] << avd_susi_delete
3)SC-2 receives quiesced response for SI2
Apr 16 16:14:41.441338 osafamfd [3370:avd_sgproc.c:0542] >>
avd_su_si_assign_evh: id:116, node:2020f, act:5,
'safSu=SU2,safSg=SGONE,safApp=TWONAPP', 'safSi=TWONSI2,safApp=TWONAPP', ha:3,
err:1, single:0
It sends quiesced to SI1.
Apr 16 16:14:41.441545 osafamfd [3370:avd_siass.c:0599] >> avd_susi_mod_send:
SI 'safSi=TWONSI1,safApp=TWONAPP', SU 'safSu=SU2,safSg=SGONE,safApp=TWONAPP'
ha_state:3
4)SC-2 recevies quisced response for SI1
Apr 16 16:14:41.529420 osafamfd [3370:avd_sgproc.c:0542] >>
avd_su_si_assign_evh: id:118, node:2020f, act:5,
'safSu=SU2,safSg=SGONE,safApp=TWONAPP', 'safSi=TWONSI1,safApp=TWONAPP', ha:3,
err:1, single:0
and it sends delete to SU2
Apr 16 16:14:41.529605 osafamfd [3370:avd_sgproc.c:1963] >>
avd_sg_su_si_del_snd: 'safSu=SU2,safSg=SGONE,safApp=TWONAPP'
5)SC-2 receives su oper state evh for SU2:
Apr 16 16:14:41.729018 osafamfd [3370:avd_sgproc.c:0258] >>
avd_su_oper_state_evh: id:123, node:2020f,
'safSu=SU2,safSg=SGONE,safApp=TWONAPP' state:2
SC-2 receives deletion response for
Apr 16 16:14:42.546234 osafamfd [3370:avd_sgproc.c:0542] >>
avd_su_si_assign_evh: id:124, node:2020f, act:4,
'safSu=SU2,safSg=SGONE,safApp=TWONAPP', '', ha:3, err:1, single:0
SUSIs are deleted in SU2 and SG becomes stable:
Apr 16 16:14:42.547428 osafamfd [3370:avd_sgproc.c:1767] <<
avd_sg_su_asgn_del_util
Apr 16 16:14:42.547439 osafamfd [3370:avd_sg2Nfsm.c:2794] TR sg_fsm_state 4 => 0
On SC-1:
1)Status of counters when SC-1 sends delete to SU1:
Apr 16 16:14:33.491480 osafamfd [2791:avd_si.c:1327] TR
safSi=TWONSI1,safApp=TWONAPP saAmfSINumCurrStandbyAssignments=0
Apr 16 16:14:33.494378 osafamfd [2791:avd_si.c:1327] TR
safSi=TWONSI2,safApp=TWONAPP saAmfSINumCurrStandbyAssignments=0
Apr 16 16:14:33.496996 osafamfd [2791:avd_si.c:1327] TR
safSi=TWONSI3,safApp=TWONAPP saAmfSINumCurrStandbyAssignments=0
Apr 16 16:14:33.499936 osafamfd [2791:avd_si.c:1327] TR
safSi=TWONSI4,safApp=TWONAPP saAmfSINumCurrStandbyAssignments=0
Apr 16 16:14:33.503912 osafamfd [2791:avd_si.c:1327] TR
safSi=TWONSI5,safApp=TWONAPP saAmfSINumCurrStandbyAssignments=0
2)While giving quiesced counter status at SC-1 after getting responses for
quiesced assignments:
Apr 16 16:14:33.478579 osafamfd [2791:avd_si.c:1310] TR
safSi=TWONSI4,safApp=TWONAPP saAmfSINumCurrActiveAssignments=0
Apr 16 16:14:33.483648 osafamfd [2791:avd_si.c:1310] TR
safSi=TWONSI5,safApp=TWONAPP saAmfSINumCurrActiveAssignments=0
Apr 16 16:14:34.090054 osafamfd [2791:avd_si.c:1310] TR
safSi=TWONSI3,safApp=TWONAPP saAmfSINumCurrActiveAssignments=0
Apr 16 16:14:34.201601 osafamfd [2791:avd_si.c:1310] TR
safSi=TWONSI2,safApp=TWONAPP saAmfSINumCurrActiveAssignments=0
Assignment status in SC-1 AMF traces:
Apr 16 16:14:33.479155 osafamfd [2791:avd_si.c:1265] TR
'safSi=TWONSI4,safApp=TWONAPP' FULLY_ASSIGNED => PARTIALLY_ASSIGNED
Apr 16 16:14:33.484006 osafamfd [2791:avd_si.c:1265] TR
'safSi=TWONSI5,safApp=TWONAPP' FULLY_ASSIGNED => PARTIALLY_ASSIGNED
Apr 16 16:14:33.491722 osafamfd [2791:avd_si.c:1265] TR
'safSi=TWONSI1,safApp=TWONAPP' FULLY_ASSIGNED => PARTIALLY_ASSIGNED
Apr 16 16:14:33.494727 osafamfd [2791:avd_si.c:1265] TR
'safSi=TWONSI2,safApp=TWONAPP' FULLY_ASSIGNED => PARTIALLY_ASSIGNED
Apr 16 16:14:33.497463 osafamfd [2791:avd_si.c:1265] TR
'safSi=TWONSI3,safApp=TWONAPP' FULLY_ASSIGNED => PARTIALLY_ASSIGNED
Apr 16 16:14:33.500213 osafamfd [2791:avd_si.c:1265] TR
'safSi=TWONSI4,safApp=TWONAPP' PARTIALLY_ASSIGNED => UNASSIGNED
Apr 16 16:14:33.504231 osafamfd [2791:avd_si.c:1265] TR
'safSi=TWONSI5,safApp=TWONAPP' PARTIALLY_ASSIGNED => UNASSIGNED
Apr 16 16:14:34.090415 osafamfd [2791:avd_si.c:1265] TR
'safSi=TWONSI3,safApp=TWONAPP' PARTIALLY_ASSIGNED => UNASSIGNED
Apr 16 16:14:34.201817 osafamfd [2791:avd_si.c:1265] TR
'safSi=TWONSI2,safApp=TWONAPP' PARTIALLY_ASSIGNED => UNASSIGNED
On SC-2:
While giving quiesced couter status by SC-2 counters status for SI1:
Apr 16 16:14:41.441644 osafamfd [3370:avd_si.c:1310] TR
safSi=TWONSI1,safApp=TWONAPP saAmfSINumCurrActiveAssignments=0
Apr 16 16:14:41.441676 osafamfd [3370:avd_si.c:1265] TR
'safSi=TWONSI1,safApp=TWONAPP' PARTIALLY_ASSIGNED => UNASSIGNED
Thus in the logs, there is no evidence that some SI is in partial assigned
status.
At the same time, /etc/init.d/opensaf status given by the reporter in the
description does not list
any SUSI related to this application.
Thus it seems an invalid issue.
Please check if the logs provided are correct or reproduce the issue and
provide traces after reproduction.
---
** [tickets:#859] dependent assignments are not removed after lock of sg with
comp faults**
**Status:** unassigned
**Milestone:** future
**Created:** Wed Apr 16, 2014 10:56 AM UTC by surender khetavath
**Last Updated:** Wed Apr 16, 2014 10:56 AM UTC
**Owner:** nobody
changeset : 5143
model : 2n
configuration : 1App,1SG,5SUs with 3comps each, 5SIs with 3CSIs each
si-si deps configured as SI1<-Si2<-SI3<-SI4 resp
SU1 mapped to SC-1,SU2 to SC-2,SU3 to pl-3 and SU4,5 to PL-4.
case:
1) lock the sg
2) unlock the sg. in the standby cbk report error on self comp
3) error escalated to nodefailover on SC-1 and node rebooted.
The assignments were not removed as seen below
safSi=TWONSI3,safApp=TWONAPP
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
safSi=TWONSI4,safApp=TWONAPP
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)
safSi=TWONSI5,safApp=TWONAPP
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)
safSi=TWONSI2,safApp=TWONAPP
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=PARTIALLY_ASSIGNED(3)
safSi=TWONSI1,safApp=TWONAPP
saAmfSIAdminState=UNLOCKED(1)
saAmfSIAssignmentState=UNASSIGNED(1)
/etc/init.d/opensafd status
safSISU=safSu=SC-2\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed2,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-2\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=PL-3\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed3,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=PL-5\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed5,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=PL-4\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed4,safApp=OpenSAF
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SC-1\,safSg=2N\,safApp=OpenSAF,safSi=SC-2N,safApp=OpenSAF
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SC-1\,safSg=NoRed\,safApp=OpenSAF,safSi=NoRed1,safApp=OpenSAF
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.------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
