changeset:   4521:29e5315f5538
branch:      opensaf-4.3.x
parent:      4509:d6e7b425c67b
user:        [email protected]
date:        Fri Sep 27 10:00:50 2013 +0530
summary:     amfnd: terminate comps when failed NPI SU is in TERMINATING state 
[#338]

changeset:   4522:8da824160aa7
branch:      opensaf-4.2.x
tag:         tip
parent:      4508:c2f36853642f
user:        [email protected]
date:        Fri Sep 27 10:01:26 2013 +0530
summary:     amfnd: terminate comps when failed NPI SU is in TERMINATING state 
[#338]




---

** [tickets:#338] amf: SG is in unrecoverable state when NPI SU moved from 
instantiating to termination failure state.**

**Status:** assigned
**Created:** Mon May 27, 2013 05:40 AM UTC by Praveen
**Last Updated:** Thu Sep 12, 2013 12:46 PM UTC
**Owner:** Praveen

Migrated from http://devel.opensaf.org/ticket/2252.

Brought opensaf with 4 components in NPI model.
 

1. Performed unlock-instantiation of SU1 and later unlock operation.
 

2. When unlock operation is performed, SU moved to instantiating and components 
are spawned one by one
 Oct 20 20:12:42 SLES11-SLOT-1 osafamfnd[9119]: 
'safSu=1,safSg=2N,safApp=pinv-demo' Presence State UNINSTANTIATED => 
INSTANTIATING
 Oct 20 20:12:42 SLES11-SLOT-1 logger: spawning the 
safComp=pinvDemo,safSu=1,safSg=2N,safApp=pinv-demo start 
Oct 20 20:12:50 SLES11-SLOT-1 logger: spawning the 
safComp=pinvDemo2,safSu=1,safSg=2N,safApp=pinv-demo start 
Oct 20 20:12:58 SLES11-SLOT-1 logger: spawning the 
safComp=pinvDemo3,safSu=1,safSg=2N,safApp=pinv-demo start 


3) For the first component, error is reported with component restart as recovery
 Oct 20 20:12:59 SLES11-SLOT-1 osafamfnd[9119]: 
'safComp=pinvDemo,safSu=1,safSg=2N,safApp=pinv-demo' faulted due to 
'errorReport(1)' : Recovery is 'componentRestart(2)'
 Oct 20 20:12:59 SLES11-SLOT-1 logger: spawning the 
safComp=pinvDemo,safSu=1,safSg=2N,safApp=pinv-demo clean 


4) clean up of first component failed, and component moved to termination 
failure
 Oct 20 20:13:09 SLES11-SLOT-1 osafamfnd[9119]: Cleanup of 
'safComp=pinvDemo,safSu=1,safSg=2N,safApp=pinv-demo' failed
 Oct 20 20:13:09 SLES11-SLOT-1 osafamfnd[9119]: Reason:'Script did not exit 
within time'
 Oct 20 20:13:09 SLES11-SLOT-1 osafamfnd[9119]: SU Failover trigerred for 
'safSu=1,safSg=2N,safApp=pinv-demo': Failed component: 
'safComp=pinvDemo,safSu=1,safSg=2N,safApp=pinv-demo'
 Oct 20 20:13:09 SLES11-SLOT-1 osafamfnd[9119]: 
'safSu=1,safSg=2N,safApp=pinv-demo' Presence State INSTANTIATING => 
TERMINATION_FAILED
 

4) unlock of other SU2 failed with following error.
 

Oct 20 20:14:23 SLES11-SLOT-1 osafamfd[9109]: Admin operation is already going
 

So the entire SG is in unrecoverable and unusable state.


Changed 19 months ago by srikanth 







Similar kind of scenario is observed when SU moves from instantiating to 
terminating state.
 

1)All the SU's are in unlocked state and si is in locked state.
 

2) when Si is unlocked, SU moved to instantiating 
Oct 21 14:38:50 SLES11-SLOT-1 osafamfnd[5095]: 
'safSu=1,safSg=2N,safApp=pinv-demo' Presence State UNINSTANTIATED => 
INSTANTIATING
 Oct 21 14:38:50 SLES11-SLOT-1 logger: spawning the 
safComp=pinvDemo,safSu=1,safSg=2N,safApp=pinv-demo start 
Oct 21 14:38:58 SLES11-SLOT-1 logger: spawning the 
safComp=pinvDemo2,safSu=1,safSg=2N,safApp=pinv-demo start 


3) Failure is reported on the first component in the SU which have been moved 
to instantiated state.
 

Oct 21 14:39:00 SLES11-SLOT-1 osafamfnd[5095]: 
'safComp=pinvDemo,safSu=1,safSg=2N,safApp=pinv-demo' faulted due to 
'errorReport(1)' : Recovery is 'suFailover(11)'
 Oct 21 14:39:00 SLES11-SLOT-1 osafamfnd[5095]: 
'safSu=1,safSg=2N,safApp=pinv-demo' Presence State INSTANTIATING => TERMINATING
 

4) after the SU moved to terminating, no suFailover happened and no recovery 
action is taken.
 



Changed 19 months ago by srikanth 




changeset used is 2918 for the above scenarios in NPI 2N model



---

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.
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to