- **status**: review --> fixed
- **Milestone**: future --> 4.2.4
---
** [tickets:#491] Presence state of SU stuck in Terminating state after
shutdown**
**Status:** fixed
**Created:** Tue Jul 09, 2013 06:14 AM UTC by surender khetavath
**Last Updated:** Fri Aug 02, 2013 04:14 AM UTC
**Owner:**
changeset: 4403:ae7c318f9e61
branch: opensaf-4.2.x
parent: 4401:8e587f3ddee5
user:praveen.malv...@oracle.com
date:Fri Aug 02 16:51:11 2013 +0530
summary: amfnd: mark CSI state assigning for quiesced SI in comp restart
recovery [#491]
changeset: 4404:ac78b7b1f254
- **status**: assigned --> review
---
** [tickets:#491] Presence state of SU stuck in Terminating state after
shutdown**
**Status:** review
**Created:** Tue Jul 09, 2013 06:14 AM UTC by surender khetavath
**Last Updated:** Thu Aug 01, 2013 08:31 AM UTC
**Owner:** Praveen
Changeset : 4325
Mod
- **status**: unassigned --> assigned
- **assigned_to**: Praveen
---
** [tickets:#491] Presence state of SU stuck in Terminating state after
shutdown**
**Status:** assigned
**Created:** Tue Jul 09, 2013 06:14 AM UTC by surender khetavath
**Last Updated:** Tue Jul 30, 2013 09:27 AM UTC
**Owner
Attached configuration (AppConfig-2N_2Comp_2SI_2CSI.xml_491_5sis_1) can be used
to reproduce the issue.
AppConfig-2N.xml is extended to prepare the configuration.
Besides this one change in amf_demo.c is required for reproducing it.
Here is the patch for amf_demo.c in default branch:
diff --gi
Here all the three components faulted three times due to
"qscingCompleteTimeout" with recovery componentrestart.
Further faults in comp3 and comp2 led to sufailover escalation and AMFND called
clean up script for comp3 and comp1.
As a part of recovery AMFD sent quiesced assignments for the SIs ho
---
** [tickets:#491] Presence state of SU stuck in Terminating state after
shutdown**
**Status:** unassigned
**Created:** Tue Jul 09, 2013 06:14 AM UTC by surender khetavath
**Last Updated:** Tue Jul 09, 2013 06:14 AM UTC
**Owner:** nobody
Changeset : 4325
Model : TWON
Configuration: 1SG,5S
