Attach amfd trace, some outlined log
Failover SU4, assign ACTIVE to SU5
~~~
Jul 12 14:03:25.175532 osafamfd [268:268:src/amf/amfd/sg_2n_fsm.cc:3379] >>
node_fail: 'safSu=SU4,safSg=AmfDemoTwon,safApp=AmfDemoTwon', 1
Jul 12 14:03:25.175759 osafamfd [268:268:src/amf/amfd/sgproc.cc:2443] >>
avd_sg_su_si_mod_snd: 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemoTwon', state 1
~~~
At this stage, amfd receives assignment response for previous STANDBY
assignment of SU5, amfd ignores it so the su_cnt_admin_oper is not decreased
~~~
Jul 12 14:03:30.504225 osafamfd [268:268:src/amf/amfd/sgproc.cc:1172] >>
avd_su_si_assign_evh: id:58, node:2050f, act:2,
'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemoTwon',
Jul 12 14:03:30.504661 osafamfd [268:268:src/amf/amfd/sgproc.cc:1484] IN
avd_su_si_assign_evh: assign susi not in proper state 5 1 2
Jul 12 14:03:30.504665 osafamfd [268:268:src/amf/amfd/sgproc.cc:1486] IN
avd_su_si_assign_evh: safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemoTwon
safSi=AmfDemoTwon,safApp=AmfDemoTwon
Jul 12 14:03:30.504669 osafamfd [268:268:src/amf/amfd/sgproc.cc:1778] <<
avd_su_si_assign_evh
Jul 12 14:03:30.505855 osafamfd [268:268:src/amf/amfd/sgproc.cc:1172] >>
avd_su_si_assign_evh: id:59, node:2050f, act:2,
'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemoTwon',
Jul 12 14:03:30.506003 osafamfd [268:268:src/amf/amfd/sgproc.cc:1484] IN
avd_su_si_assign_evh: assign susi not in proper state 5 1 2
Jul 12 14:03:30.506006 osafamfd [268:268:src/amf/amfd/sgproc.cc:1486] IN
avd_su_si_assign_evh: safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemoTwon
safSi=AmfDemoTwonDep1,safApp=AmfDemoTwon
Jul 12 14:03:30.506038 osafamfd [268:268:src/amf/amfd/sgproc.cc:1778] <<
avd_su_si_assign_evh
Jul 12 14:03:30.506516 osafamfd [268:268:src/amf/amfd/sgproc.cc:1172] >>
avd_su_si_assign_evh: id:60, node:2050f, act:2,
'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemoTwon',
'safSi=AmfDemoTwonDep2,safApp=AmfDemoTwon', ha:2, err:1, single:0
Jul 12 14:03:30.506735 osafamfd [268:268:src/amf/amfd/sgproc.cc:1484] IN
avd_su_si_assign_evh: assign susi not in proper state 5 1 2
Jul 12 14:03:30.506739 osafamfd [268:268:src/amf/amfd/sgproc.cc:1486] IN
avd_su_si_assign_evh: safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemoTwon
safSi=AmfDemoTwonDep2,safApp=AmfDemoTwon
Jul 12 14:03:30.506742 osafamfd [268:268:src/amf/amfd/sgproc.cc:1778] <<
avd_su_si_assign_evh
~~~
amfd receives ACTIVE assignment response which is originated from SU failover,
this assignment response is for all SUs. The su_cnt_admin_oper is decreased by
1 only
~~~
Jul 12 14:03:30.507111 osafamfd [268:268:src/amf/amfd/sgproc.cc:1172] >>
avd_su_si_assign_evh: id:61, node:2050f, act:5,
'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemoTwon', '', ha:1, err:1, single:0
Jul 12 14:03:30.525188 osafamfd [268:268:src/amf/amfd/sgproc.cc:1682] TR
node:'safAmfNode=PL-5,safAmfCluster=myAmfCluster', su_cnt_admin_oper:2
Jul 12 14:03:30.525192 osafamfd [268:268:src/amf/amfd/sgproc.cc:0359] >>
process_su_si_response_for_ng: 'safSu=SU5,safSg=AmfDemoTwon,safApp=AmfDemoTwon'
Jul 12 14:03:30.525199 osafamfd [268:268:src/amf/amfd/sgproc.cc:0458] <<
process_su_si_response_for_ng
~~~
The last assignment response comes to amfd from STANDBY assignment of SU, which
is from SU failover, the node_oper_list still has PL5, thus amfd does not reply
the admin unlock ng
~~~
Jul 12 14:03:30.536971 osafamfd [268:268:src/amf/amfd/sgproc.cc:1172] >>
avd_su_si_assign_evh: id:85, node:2040f, act:2,
'safSu=SU4,safSg=AmfDemoTwon,safApp=AmfDemoTwon',
'safSi=AmfDemoTwonDep2,safApp=AmfDemoTwon', ha:2, err:1, single:0
Jul 12 14:03:30.541013 osafamfd [268:268:src/amf/amfd/sgproc.cc:1682] TR
node:'safAmfNode=PL-4,safAmfCluster=myAmfCluster', su_cnt_admin_oper:0
Jul 12 14:03:30.541016 osafamfd [268:268:src/amf/amfd/sgproc.cc:0359] >>
process_su_si_response_for_ng: 'safSu=SU4,safSg=AmfDemoTwon,safApp=AmfDemoTwon'
Jul 12 14:03:30.541020 osafamfd [268:268:src/amf/amfd/sgproc.cc:0430] TR
node_oper_list size:1
Jul 12 14:03:30.541022 osafamfd [268:268:src/amf/amfd/sgproc.cc:0458] <<
process_su_si_response_for_ng
~~~
Attachments:
-
[amfd_trace.tgz](https://sourceforge.net/p/opensaf/tickets/_discuss/thread/d8ef4294/cf6d/attachment/amfd_trace.tgz)
(952.3 kB; application/x-compressed)
---
** [tickets:#2526] amfd: Command unlock nodegroup timeout if su failover is
escalated**
**Status:** unassigned
**Milestone:** 5.17.10
**Labels:** nodegroup timeout
**Created:** Wed Jul 12, 2017 04:23 AM UTC by Minh Hon Chau
**Last Updated:** Wed Jul 12, 2017 04:23 AM 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 [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.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
