- **status**: assigned --> fixed
- **Comment**:
commit db5e0c24ff713126d2912b6c3ec59cfbcfbda491 (HEAD -> develop,
origin/develop)
Author: thang.d.nguyen <[email protected]>
Date: Thu Aug 13 12:02:39 2020 +1000
amfnd: handle component failover during SURestart [#3207]
During SURestart, another compoenent is failovered. The
SU-SI modify event message need buffering to process later.
The new active assignment on SU need processing after it is
instantiated.
---
** [tickets:#3207] amf: si in PARTIALLY_ASSIGNED after component failover**
**Status:** fixed
**Milestone:** 5.20.08
**Created:** Wed Jul 29, 2020 07:14 AM UTC by Thang Duc Nguyen
**Last Updated:** Wed Jul 29, 2020 07:14 AM UTC
**Owner:** Thang Duc Nguyen
Deploy 2N model app
1. Active asignment on SC-1, standby assignment on SC-2
2. Trigger SU restart on SC-2, component failover on SC-1. SU on SC-2 is stuck
during instantiating.
3. Active assigment move on SC-2 while SU is not instantiated
4. Then SI is not assigned standy on SC-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
