- **Milestone**: 5.19.01 --> future
---
** [tickets:#2526] amfd: Command unlock nodegroup timeout if su failover is
escalated (>= 2SIs)**
**Status:** unassigned
**Milestone:** future
**Labels:** nodegroup timeout
**Created:** Wed Jul 12, 2017 04:23 AM UTC by Minh Hon Chau
**Last Updated:** Wed Jan 09, 2019 09:23 PM UTC
**Owner:** nobody
**Attachments:**
-
[app3_twon3su3si.xml](https://sourceforge.net/p/opensaf/tickets/2526/attachment/app3_twon3su3si.xml)
(14.6 kB; text/xml)
- Configuration: 2N app, 3SI (model is attached), SU4/SU5 are hosted on PL4/PL5
respectively
- Steps:
. Create nodegroup consists of PL4/PL5
. Unlock ng
. SU4 is assigned ACTIVE
. While component of SU5 is being assigned STANDBY, kill a component of SU4 to
escalate to a SuFailover
. SU4 is now getting STANDBY assignment, SU5 is getting ACTIVE assignment
. But the command unlock ng is being hold until TIMEOUT
Note: Repeat the same test with only **1 SI**, the command unlock ng returns OK
---
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