- **status**: assigned --> not-reproducible
- **Comment**:
After implmentation of sufailover feature (for NPI SU component failover is
sufailover), this issue is not applicable to 4.4 and default branch. Still I
tried to reproduce on default branch and everything is working fine.
Regarding 4.3 branch, here also it is not reproducible and clean up/termination
of all components is successful.
Attached are the logs in default and 4.3 branch after successful verifying
steps.
Hence closing this issue as not-reproducible.
---
** [tickets:#186] Some of NPI components are not cleaned up when suFailover is
triggered on SU in terminating state**
**Status:** not-reproducible
**Milestone:** 4.3.3
**Created:** Tue May 14, 2013 07:22 AM UTC by Nagendra Kumar
**Last Updated:** Mon Jun 16, 2014 11:33 AM UTC
**Owner:** Praveen
Migrated from http://devel.opensaf.org/ticket/2257
Brought up opensaf with change set 2918 with NPI 2N model fully up.
When active SU is locked and standby SU is in in service, component failover is
reported on one of the component in instantiated state.
In the current scenario, 1st and 2nd components in SU are cleaned up. And when
4th component is reported with suFailover, 3rd component is not cleaned up.
Below is the snippet from syslog:
Oct 21 15:09:55 SLES11-SLOT-1 osafamfnd[4289]:
'safSu=1,safSg=2N,safApp=pinv-demo' Presence State INSTANTIATED => TERMINATING
Oct 21 15:09:55 SLES11-SLOT-1 logger: spawning the
safComp=pinvDemo4,safSu=1,safSg=2N,safApp=pinv-demo stop
Oct 21 15:09:55 SLES11-SLOT-1 osafamfnd[4289]: Termination of
'safComp=pinvDemo4,safSu=1,safSg=2N,safApp=pinv-demo' failed
Oct 21 15:09:55 SLES11-SLOT-1 osafamfnd[4289]: Reason:'Script did not exit
within time'
Oct 21 15:09:55 SLES11-SLOT-1 logger: spawning the
safComp=pinvDemo4,safSu=1,safSg=2N,safApp=pinv-demo clean
Oct 21 15:10:02 SLES11-SLOT-1 osafamfnd[4289]:
'safComp=pinvDemo,safSu=1,safSg=2N,safApp=pinv-demo' faulted due to
'errorReport(1)' : Recovery is 'suFailover(11)'
Oct 21 15:10:02 SLES11-SLOT-1 logger: spawning the
safComp=pinvDemo,safSu=1,safSg=2N,safApp=pinv-demo clean
Oct 21 15:10:02 SLES11-SLOT-1 osafamfnd[4289]: Comp DB record lookup failed:
Oct 21 15:10:03 SLES11-SLOT-1 logger: spawning the
safComp=pinvDemo3,safSu=1,safSg=2N,safApp=pinv-demo stop
Oct 21 15:10:03 SLES11-SLOT-1 osafamfnd[4289]: Termination of
'safComp=pinvDemo3,safSu=1,safSg=2N,safApp=pinv-demo' failed
Oct 21 15:10:03 SLES11-SLOT-1 osafamfnd[4289]: Reason:'Script did not exit
within time'
Oct 21 15:10:03 SLES11-SLOT-1 logger: spawning the
safComp=pinvDemo3,safSu=1,safSg=2N,safApp=pinv-demo clean
Oct 21 15:10:10 SLES11-SLOT-1 osafamfnd[4289]:
'safSu=1,safSg=2N,safApp=pinv-demo' Presence State TERMINATING => UNINSTANTIATED
Here safComp=pinvDemo3,safSu=1,safSg=2N,safApp=pinv-demo did not get cleaned up.
Changed 19 months ago by srikanth ΒΆ
In the above scenario as the component doesn't get cleaned up, the presence
state of the component is not set to uninstantiated and is still having
instantiated state.
when this SU takes active role if si-swap is invoked , component will not be
spawned next time ( because of bug ) and further components will not be
spawned.
Finally in this SU, some of the components will be in instantiated and other
components will be in uninstantiated state. HA state of this SU will be struck
in STANDBY and old active SU is struck in quiesced state.
Oct 21 15:17:34.874279 osafamfnd [4289:avnd_clc.c:0756] >>
avnd_comp_clc_fsm_run: Comp
'safComp=pinvDemo2,safSu=1,safSg=2N,safApp=pinv-demo', Ev '1'
Oct 21 15:17:34.874279 osafamfnd [4289:avnd_clc.c:0803] T1
'safComp=pinvDemo2,safSu=1,safSg=2N,safApp=pinv-demo':Entering CLC FSM:
presence state:'SA_AMF_PRESENCE_INSTANTIATED(3)',
Event:'AVND_COMP_CLC_PRES_FSM_EV_INST_SUCC'
Oct 21 15:17:34.874279 osafamfnd [4289:avnd_clc.c:0824] T1 Exited CLC FSM
Oct 21 15:17:34.874279 osafamfnd [4289:avnd_clc.c:0826] T1
'safComp=pinvDemo2,safSu=1,safSg=2N,safApp=pinv-demo':FSM Enter presence state:
'SA_AMF_PRESENCE_INSTANTIATED(3)':FSM Exit presence
state:SA_AMF_PRESENCE_INSTANTIATED(3)
---
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 fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
