- **status**: assigned --> accepted
- Attachments has changed:
Diff:
~~~~
--- old
+++ new
@@ -1 +1,3 @@
createAppTestApp.sh (15.8 kB; text/x-shellscript)
+messages (11.2 kB; application/octet-stream)
+osafamfd (452.8 kB; application/octet-stream)
~~~~
- **Milestone**: 4.7.2 --> 5.1.RC2
- **Comment**:
With the configuration provided by the creater, issue cannot be reproduced as
comps recovery is comprestart.
However, based on bt provided, issue can be reproduced with following steps:
1)Change the configuration provided by the ticket creater by hosting SU1 on
SC-2 and other SUs on SC-1. Enable disableRestart flag for all the comps.
2)Bring the configuration up. SI1 will become acitve in SU1 on SC-2 and standby
in SU2 on SC-1 .
3)Create a nodegroup with SC-1 and SC-2.
4)Lock the NG, delay response for removal callback for SI1 on SU2. Respond for
quiesced callback for SI1 on SU1 but delay removal callback.
5)kill comp in SU1 that has delayed removal of Si1.
6)AMFD will try to failover of SI1 but it could not find any In-service. It
tries to send again removal of assigments to SU2 and asserts.
---
** [tickets:#2022] AMF : amfd asserted for NG lock operation ( quiesced timeout
- Nway model))**
**Status:** accepted
**Milestone:** 5.1.RC2
**Created:** Sat Sep 10, 2016 09:58 AM UTC by Srikanth R
**Last Updated:** Thu Sep 15, 2016 05:41 AM UTC
**Owner:** Praveen
**Attachments:**
-
[createAppTestApp.sh](https://sourceforge.net/p/opensaf/tickets/2022/attachment/createAppTestApp.sh)
(15.8 kB; text/x-shellscript)
-
[messages](https://sourceforge.net/p/opensaf/tickets/2022/attachment/messages)
(11.2 kB; application/octet-stream)
-
[osafamfd](https://sourceforge.net/p/opensaf/tickets/2022/attachment/osafamfd)
(452.8 kB; application/octet-stream)
Environment details
------------------
OS : Suse 64bit
Changeset : 7997 ( 5.1.FC)
Setup : 5 nodes ( 2 controllers and 3 payloads with headless feature enabled &
no PBE )
AMF Application : NPM model with SUs mapped on SC-2,PL-3,PL-4
Summary :
------------------
AMFD on both controllers asserted, if Nway application failed in CSI SET
QUIESCED callback in lock operation of node group
Steps followed & Observed behaviour
------------------
-> Hosted nway application on PL-3,PL-4 and SC-2 and brought up the
application. Configuration is attached to the ticket.
-> Created a node group with all the three nodes.
-> Ensured that one of component will not respond to quiesced callback
-> Now performed the lock operation on the node group
-> amfd on both controllers asserted with the following back trace.
0 0x00007f66fbc6fb55 in raise () from /lib64/libc.so.6
1 0x00007f66fbc71131 in abort () from /lib64/libc.so.6
2 0x00007f66fda6816a in __osafassert_fail (__file=0x51214d "su.cc",
__line=2022, __func=0x513aa0 "dec_curr_stdby_si", __assertion=0x51355f
"saAmfSUNumCurrStandbySIs > 0") at sysf_def.c:281
3 0x00000000004d68cd in AVD_SU::dec_curr_stdby_si (this=0x7ccf40) at su.cc:2022
4 0x00000000004be804 in avd_susi_update_assignment_counters (susi=0x78c670,
action=AVSV_SUSI_ACT_DEL, current_ha_state=0, new_ha_state=0) at siass.cc:783
5 0x00000000004be59b in avd_susi_del_send (susi=0x78c670) at siass.cc:714
6 0x00000000004af12e in avd_sg_nway_node_fail_stable (cb=0x751b80,
su=0x800470, susi=0x0) at sg_nway_fsm.cc:3022
7 0x00000000004b025d in avd_sg_nway_node_fail_sg_realign (cb=0x751b80,
su=0x800470) at sg_nway_fsm.cc:3493
8 0x00000000004a8042 in SG_NWAY::node_fail (this=0x797c50, cb=0x751b80,
su=0x800470) at sg_nway_fsm.cc:497
9 0x00000000004b209e in sg_su_failover_func (su=0x800470) at sgproc.cc:525
10 0x00000000004b2d16 in avd_su_oper_state_evh (cb=0x751b80,
evt=0x7f66f4002940) at sgproc.cc:838
11 0x0000000000450ba9 in process_event (cb_now=0x751b80, evt=0x7f66f4002940) at
main.cc:768
12 0x00000000004508cd in main_loop () at main.cc:689
13 0x0000000000450e43 in main (argc=2, argv=0x7fff0f81ab18) at main.cc:841
---
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
