#3288 fmd: failed during setting role from standby to active

[Huu The Truong]

After the standby SC down then another SC is promoted to became
the new standby SC.
2021-09-28 07:00:35.950 SC-2 osaffmd[392]: NO Node Down event for node id 2040f:
2021-09-28 07:00:35.950 SC-2 osaffmd[392]: NO Current role: STANDBY

At that time, the new standby SC received peer info response from old standby SC is needed promote to became the active SC.
2021-09-28 07:00:35.972 SC-2 osaffmd[392]: NO Controller Failover: Setting role to ACTIVE
2021-09-28 07:00:35.972 SC-2 osafrded[382]: NO RDE role set to ACTIVE
...
2021-09-28 07:00:36.113 SC-2 osafclmd[448]: NO ACTIVE request
2021-09-28 07:00:36.114 SC-2 osaffmd[392]: NO Controller promoted. Stop supervision timer

While an another active SC is alive lead to the standby SC reboots itselft because cluster has only one active SC.
2021-09-28 07:00:36.117 SC-2 osafamfd[459]: ER FAILOVER StandBy --> Active FAILED, Standby OUT OF SYNC
2021-09-28 07:00:36.117 SC-2 osafamfd[459]: Rebooting OpenSAF NodeId = 0 EE Name = No EE Mapped, Reason: FAILOVER failed, OwnNodeId = 2020f, SupervisionTime = 60

[Mohan Kanakam]

Hi Huu The Truong,
I tried to reproduce the issue but i did not succeed.
I configured cluster with 4 nodes(SC-1(ACTIVE),SC-2(STANDBY),SC-3(QUIESCED),SC-4(QUIESCED)) and manually shutdown the SC-2(STANDBY) node to reproduce the issue.
Thanks
Mohan