- **status**: review --> fixed
- **Comment**:
changeset: 8314:10aac604ba15
branch: opensaf-5.0.x
parent: 8311:9cee81b39c47
user: Praveen Malviya <[email protected]>
date: Tue Nov 15 11:52:16 2016 +0530
summary: amfd: avoid active SI failover during su or node failover
recovery, N-WAY model[#1944]
changeset: 8315:a80c58cc2159
branch: opensaf-5.1.x
parent: 8312:c365dd1e0992
user: Praveen Malviya <[email protected]>
date: Tue Nov 15 11:52:37 2016 +0530
summary: amfd: avoid active SI failover during su or node failover
recovery, N-WAY model[#1944]
changeset: 8316:96eb3da2334d
tag: tip
parent: 8313:fa6b413693e3
user: Praveen Malviya <[email protected]>
date: Tue Nov 15 11:52:48 2016 +0530
summary: amfd: avoid active SI failover during su or node failover
recovery, N-WAY model[#1944]
[staging:10aac6]
[staging:a80c58]
[staging:96eb3d]
---
** [tickets:#1944] amf: two actives for same SI after sufailover recovery
during su lock/shutdown, NWAY.**
**Status:** fixed
**Milestone:** 5.0.2
**Created:** Tue Aug 09, 2016 09:23 AM UTC by Praveen
**Last Updated:** Fri Sep 30, 2016 06:55 AM UTC
**Owner:** Praveen
**Attachments:**
-
[two_actives.tgz](https://sourceforge.net/p/opensaf/tickets/1944/attachment/two_actives.tgz)
(69.1 kB; application/x-compressed)
Attached are traces and conf.
steps to reproduce:
1)Bring the configuration up.
2)Lock active SU.
3)While processing remove callback, one comp must fault sufailover recovery.
4)Amf will make Su3 also active for both the SIs when Su2 is already make
active after quiesced assignments.
Assignments before su lock
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=STANDBY(2)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU1\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
Assignments after SU lock:
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU2\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
safSISU=safSu=SU3\,safSg=AmfDemo\,safApp=AmfDemo1,safSi=AmfDemo1,safApp=AmfDemo1
saAmfSISUHAState=ACTIVE(1)
Issue will be applicable to Nore lock/shutdown also.
---
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
