- **status**: review --> fixed
- **Comment**:

changeset:   8195:967e479b7c42
branch:      opensaf-5.0.x
user:        Praveen Malviya <praveen.malv...@oracle.com>
date:        Fri Oct 07 16:57:22 2016 +0530
summary:     amfnd: send recovery request to amfd for term-failed PI su [#2047] 
V2

changeset:   8196:88f6b4d6e234
branch:      opensaf-5.1.x
parent:      8193:78c53fa41138
user:        Praveen Malviya <praveen.malv...@oracle.com>
date:        Fri Oct 07 16:57:57 2016 +0530
summary:     amfnd: send recovery request to amfd for term-failed PI su [#2047] 
V2

changeset:   8197:69f86b9bddb0
tag:         tip
parent:      8192:c219f1b059cb
user:        Praveen Malviya <praveen.malv...@oracle.com>
date:        Fri Oct 07 16:58:07 2016 +0530
summary:     amfnd: send recovery request to amfd for term-failed PI su [#2047] 
V2





---

** [tickets:#2047] amf: SG unstable when NPI comp in PI SU moves to TERM_FAILED 
state during fresh assignments.**

**Status:** fixed
**Milestone:** 5.0.2
**Created:** Mon Sep 19, 2016 11:31 AM UTC by Praveen
**Last Updated:** Tue Sep 27, 2016 12:54 PM UTC
**Owner:** Praveen
**Attachments:**

- 
[pinpi_issue.tgz](https://sourceforge.net/p/opensaf/tickets/2047/attachment/pinpi_issue.tgz)
 (21.9 kB; application/x-compressed)


Conf: 2N model, one NPI and one PI comp in SU.
Steps to reproduce:
1)Add application using immcfg command.
2)Lock SG.
3)Unlock-in and unlock SUs.
4)Make provisions so that instantiation and clean up scripts of NPI comp 
returns with non-zero status.
5)Unlock SG.
When SG is unlocked, AMFND initiates active assignments by issuing callback to 
PI comp and by instantiating NPI component. After instantiation failure of NPI 
comp, AMFND tries to clean up it. Cleanup fails. AMFND marks comp and SU in 
TERM_FAILED state and terminates PI comp also, but AMFND neither responds to 
AMFD for the completion of assignment nor it sends any recovery request. 
Because of this SG remains unstable in REALIGN state.In this state, no admin 
operation is allowed.
Attached are traces and configuration.
Even though issue seems to be similar to #538, it is different in one aspect. 
In #538, SU moves to TERM_FAILED state and there is possibiltiy of 
failover/switchover as standby assignments are present.
In the present case, it happened during initial assignments and thus there is 
no standby to switchover/failover to.


---

Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to