commit f78101b9a5021466bdf40dea67639f3e8b94048c (HEAD -> develop,
origin/develop, ticket-3017)
Author: thang.d.nguyen <thang.d.ngu...@dektech.com.au>
Date: Thu Mar 5 14:21:48 2020 +0700
fm: ignore unexpected event on standby node [#3017]
In roaming sc, when the standby SC down, the new standby
is selected. But the amfd on the old standby is stuck.
And the new standby receives the amfd down event of old
standby.
In this case, FM should ignore events from old standby SC.
---
** [tickets:#3017] fmd: STANDBY node still do failover to ACTIVE when ACTIVE
node existed**
**Status:** review
**Milestone:** 5.20.05
**Created:** Thu Mar 14, 2019 04:57 AM UTC by Thang Duc Nguyen
**Last Updated:** Sat Feb 15, 2020 02:04 AM UTC
**Owner:** Thang Duc Nguyen
In roaming SC, shutdown standby SC to make another takes STANDBY role. During
the new node change to STANDBY, it receives the AMFD down event from the old
STANDBY and it default set role to ACTIVE instead of the ACTIVE already exist.
Situation: SC-3 (ACTIVE), SC-1 (old STANDBY), SC-2 (new STANDBY).
In syslog.
***2019-03-14 11:01:07.632 SC-2 osafimmnd[221]: NO Implementer disconnected 21
<0, 2010f(down)> (@safAmfService2010f)
2019-03-14 11:01:07.748 SC-2 osafimmnd[221]: NO Received: immadm -o 202
safRdn=immManagement,safApp=safImmService
2019-03-14 11:01:08.765 SC-2 osafamfnd[277]: NO Assigning
'safSi=SC-2N,safApp=OpenSAF' STANDBY to 'safSu=SC-2,safSg=2N,safApp=OpenSAF'
2019-03-14 11:01:08.767 SC-2 osafrded[191]: NO RDE role set to STANDBY
2019-03-14 11:01:08.770 SC-2 osafrded[191]: NO Peer up on node 0x2030f
2019-03-14 11:01:08.770 SC-2 osafrded[191]: NO Got peer info response from node
0x2030f with role ACTIVE
2019-03-14 11:01:08.810 SC-2 osafimmd[210]: NO MDS event from svcid 24
(change:3, dest:13)
2019-03-14 11:01:08.841 SC-2 osafimmd[210]: NO MDS event from svcid 24
(change:5, dest:13)
2019-03-14 11:01:08.842 SC-2 osafimmd[210]: NO MDS event from svcid 24
(change:5, dest:13)
2019-03-14 11:01:08.843 SC-2 osafimmd[210]: NO MDS event from svcid 25
(change:3, dest:568513101120729)
2019-03-14 11:01:08.844 SC-2 osafimmd[210]: NO MDS event from svcid 25
(change:3, dest:566313703976433)
2019-03-14 11:01:08.844 SC-2 osafimmd[210]: NO MDS event from svcid 25
(change:3, dest:567415988304317)
2019-03-14 11:01:08.844 SC-2 osafimmd[210]: NO MDS event from svcid 25
(change:3, dest:565213755369309)
2019-03-14 11:01:08.846 SC-2 osafimmnd[221]: NO Implementer connected: 23
(OpenSafImmPBE) <0, 2030f>
2019-03-14 11:01:08.847 SC-2 osafimmd[210]: WA IMPL-id: 0 + 1 != 24
2019-03-14 11:01:08.851 SC-2 osafsmfd[298]: NO MDS initializeforassignment:
smfdmdsinit()
2019-03-14 11:01:08.852 SC-2 osafsmfd[298]: NO MDS smfdmdsinit: mdsvdestcreate()
2019-03-14 11:01:08.854 SC-2 osafsmfd[298]: NO MDS mdsvdestcreate: VDEST created
2019-03-14 11:01:08.855 SC-2 osafsmfd[298]: NO MDS smfdmdsinit: mdsregister()
2019-03-14 11:01:08.855 SC-2 osafsmfd[298]: NO MDS mdsregister: mds
registration is done
2019-03-14 11:01:08.856 SC-2 osafsmfd[298]: NO MDS smfdmdsinit:
smfdmdschangerole()
2019-03-14 11:01:08.856 SC-2 osafsmfd[298]: NO MDS smfdmdschangerole: Setting;
arg.info.vdestchgrole.ivdest = 0xf, ncsvdaapi() rc = 1
2019-03-14 11:01:08.859 SC-2 osafsmfd[298]: NO initializeforassignment:
smfdmdsinit() Done
2019-03-14 11:01:08.867 SC-2 osafsmfd[298]: NO MDS amfcsisetcallback:
smfdmdschangerole()
2019-03-14 11:01:08.874 SC-2 osafsmfd[298]: NO MDS smfdmdschangerole: Setting;
arg.info.vdestchgrole.ivdest = 0xf, ncsvdaapi() rc = 1
2019-03-14 11:01:08.875 SC-2 osaflogd[237]: NO LOGSVDATAGROUPNAME not found
2019-03-14 11:01:08.877 SC-2 osaflogd[237]: NO LOG root directory is:
"/srv/shared/saflog"
2019-03-14 11:01:08.879 SC-2 osaflogd[237]: NO LOG data group is: ""
2019-03-14 11:01:08.881 SC-2 osafimmnd[221]: NO Implementer (applier)
connected: 24 (@safAmfService2020f) <97, 2020f>
2019-03-14 11:01:08.882 SC-2 osaflogd[237]: NO LGSMBCSVVERSION = 7
2019-03-14 11:01:08.883 SC-2 osafamfnd[277]: NO Assigned
'safSi=SC-2N,safApp=OpenSAF' STANDBY to 'safSu=SC-2,safSg=2N,safApp=OpenSAF'
2019-03-14 11:01:08.884 SC-2 osafntfimcnd[473]: logtrace: trace enabled to file
'osafntfimcn', mask=0x0
2019-03-14 11:01:09.144 SC-2 osafamfd[267]: NO osafAmfRestrictAutoRepairEnable
set to '1'
2019-03-14 11:01:09.144 SC-2 osafamfd[267]: NO osafAmfDelayNodeFailoverTimeout
set to '0'
2019-03-14 11:01:09.144 SC-2 osafamfd[267]: NO
osafAmfDelayNodeFailoverNodeWaitTimeout set to '180'
2019-03-14 11:01:09.408 SC-2 osafimmnd[221]: NO Implementer (applier)
connected: 25 (@OpenSafImmReplicatorB) <110, 2020f>
2019-03-14 11:01:09.411 SC-2 osafntfimcnd[473]: NO Started
2019-03-14 11:01:13.259 SC-2 osaffmd[200]: NO AVD down on: 2010f
2019-03-14 11:01:14.168 SC-2 osafamfd[267]: NO Cold sync complete!
2019-03-14 11:01:15.873 SC-2 osaffmd[200]: NO Node Down event for node id 2010f:
2019-03-14 11:01:15.874 SC-2 osaffmd[200]: NO Current role: STANDBY
2019-03-14 11:01:15.874 SC-2 osaffmd[200]: Rebooting OpenSAF NodeId = 131343 EE
Name = , Reason: Received Node Down for peer controller, OwnNodeId = 131599,
SupervisionTime = 60
2019-03-14 11:01:15.900 SC-2 opensafreboot: Rebooting remote node in the
absence of PLM is outside the scope of OpenSAF
2019-03-14 11:01:15.902 SC-2 osaffmd[200]: NO Controller Failover: Setting role
to ACTIVE
2019-03-14 11:01:15.903 SC-2 osafrded[191]: NO RDE role set to ACTIVE
2019-03-14 11:01:15.904 SC-2 osafrded[191]: NO Running
'/usr/local/lib/opensaf/opensafscactive' with 0 argument(s)
2019-03-14 11:01:15.908 SC-2 osafrded[191]: IN
'/usr/local/lib/opensaf/opensafscactive' exited successfully
2019-03-14 11:01:15.935 SC-2 osafimmd[210]: NO ACTIVE request
2019-03-14 11:01:15.935 SC-2 osaflogd[237]: NO ACTIVE request
2019-03-14 11:01:15.935 SC-2 osafntfd[247]: NO ACTIVE request
2019-03-14 11:01:15.936 SC-2 osafclmd[257]: NO ACTIVE request
2019-03-14 11:01:15.936 SC-2 osafamfd[267]: NO FAILOVER StandBy --> Active
2019-03-14 11:01:15.936 SC-2 osafamfnd[277]: NO AVD NEWACTIVE, adest:1
2019-03-14 11:01:15.962 SC-2 osafimmd[210]: NO MDS event from svcid 24
(change:7, dest:13)
2019-03-14 11:01:15.962 SC-2 osafimmd[210]: NO MDS event from svcid 24
(change:7, dest:13)
2019-03-14 11:01:15.983 SC-2 osafimmd[210]: NO ellectcoord invoke from
rdacallback ACTIVE
2019-03-14 11:01:15.983 SC-2 osafimmd[210]: WA IMMD not re-electing coord for
switch-over (si-swap) coord at (2030f)
2019-03-14 11:01:15.983 SC-2 osafimmnd[221]: NO Implementer disconnected 24
<97, 2020f> (@safAmfService2020f)
2019-03-14 11:01:15.984 SC-2 osafamfd[267]: ER FAILOVER StandBy --> Active
FAILED, ImplementerSet failed 14**
---
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
