- **status**: accepted --> review
---
** [tickets:#2003] amf: SG unstable when SU moves to TERM_FAILED state during
fresh assignments.**
**Status:** review
**Milestone:** 4.7.2
**Created:** Tue Sep 06, 2016 08:31 AM UTC by Praveen
**Last Updated:** Tue Sep 06, 2016 08:32 AM UTC
**Owner:** Praveen
**Attachments:**
-
[term_failed.tgz](https://sourceforge.net/p/opensaf/tickets/2003/attachment/term_failed.tgz)
(30.1 kB; application/x-compressed)
Conf: 2N model, one NPI comp in NPI 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 returns with
non-zero status.
5)Unlock SG.
When SG is unlocked, AMFND initiates active assignments by instantiating the
only component. After instantiation failure, AMFND tries to clean up the
component. Cleanup fails. AMFND marks comp and SU in TERM_FAILED state, but it
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.
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.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
