[tickets] [opensaf:tickets] #2003 amf: SG unstable when SU moves to TERM_FAILED state during fresh assignments.
--- ** [tickets:#2003] amf: SG unstable when SU moves to TERM_FAILED state during fresh assignments.** **Status:** unassigned **Milestone:** 4.7.2 **Created:** Tue Sep 06, 2016 08:31 AM UTC by Praveen **Last Updated:** Tue Sep 06, 2016 08:31 AM UTC **Owner:** nobody **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
[tickets] [opensaf:tickets] #2003 amf: SG unstable when SU moves to TERM_FAILED state during fresh assignments.
- **status**: unassigned --> accepted - **assigned_to**: Praveen - **Component**: unknown --> amf - **Part**: - --> nd --- ** [tickets:#2003] amf: SG unstable when SU moves to TERM_FAILED state during fresh assignments.** **Status:** accepted **Milestone:** 4.7.2 **Created:** Tue Sep 06, 2016 08:31 AM UTC by Praveen **Last Updated:** Tue Sep 06, 2016 08:31 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
[tickets] [opensaf:tickets] #2003 amf: SG unstable when SU moves to TERM_FAILED state during fresh assignments.
- **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
[tickets] [opensaf:tickets] #2003 amf: SG unstable when SU moves to TERM_FAILED state during fresh assignments.
- **status**: review --> fixed - **Comment**: changeset: 8016:77a9f5df113f branch: opensaf-4.7.x user:praveen.malv...@oracle.com date:Thu Sep 08 14:13:52 2016 +0530 summary: amfnd: send recovery request to amfd for term-failed su [#2003] changeset: 8017:f15bc3868b81 branch: opensaf-5.0.x parent: 8014:0b491ef33bb8 user:praveen.malv...@oracle.com date:Thu Sep 08 14:14:25 2016 +0530 summary: amfnd: send recovery request to amfd for term-failed su [#2003] changeset: 8018:466142dde156 branch: opensaf-5.1.x parent: 8013:9acf7c9aecab user:praveen.malv...@oracle.com date:Thu Sep 08 14:14:49 2016 +0530 summary: amfnd: send recovery request to amfd for term-failed su [#2003] changeset: 8019:21bf64e1130a tag: tip parent: 8012:46edfce1d524 user:praveen.malv...@oracle.com date:Thu Sep 08 14:14:59 2016 +0530 summary: amfnd: send recovery request to amfd for term-failed su [#2003] --- ** [tickets:#2003] amf: SG unstable when SU moves to TERM_FAILED state during fresh assignments.** **Status:** fixed **Milestone:** 4.7.2 **Created:** Tue Sep 06, 2016 08:31 AM UTC by Praveen **Last Updated:** Tue Sep 06, 2016 09:30 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
