- **Comment**:
Steps to reproduce the issue.
1. Deploy 2N app, 2 Comps/SU with saAmfSgtDefCompRestartMax = 0,
saAmfSutDefSUFailover = 0
2. SU1 contained compA, compB assigned ACTIVE. Sleep in instantiation script
of comp B
3. Terminate compA to trigger SU restart.
4. SU1 will TERMINATING then move to INSTANTIATING.
5. SU1 is stucked at INSTANTIATING due to compB. After comp A re-instantiated,
terminate it.
6. SU restart will be escalated to component failover. QUIESCED was assigned
to SU1.
As consequence, no failover to SU2 and no recovery for comp A. And SU1 is
stucking in INSTANTIATING presence state.
---
** [tickets:#3135] amfd: SU is stucked at INSTANTIATING/TERMINATING in presence
state**
**Status:** assigned
**Milestone:** 5.20.01
**Created:** Wed Dec 25, 2019 01:38 AM UTC by Thang Duc Nguyen
**Last Updated:** Mon Dec 30, 2019 02:11 AM UTC
**Owner:** Thang Duc Nguyen
The SU is stucked at INSTANTIATING
safSu=ma_su_1,safSg=ma_sg,safApp=ma_app
AdminState=UNLOCKED(1)
OperState=DISABLED(2)
PresenceState=INSTANTIATING(2)
ReadinessState=OUT-OF-SERVICE(1)
---
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._______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
