- Description has changed:
Diff:
~~~~
--- old
+++ new
@@ -1,3 +1,6 @@
+There is a situation, SC-1 sees SC-2 active then rde role on SC-1 changes to
QIESCED. Amfd on SC-1 has not assigned standby yet. At that time active SC-2 is
rebooted. The SI of Nored Opensaf app was assgned on SC-1 successfully on SC-1
but the SU-SI record not created by amfd.
+After SC-1 is promoted to ACTIVE but init_state of amfd can not move to
AVD_INIT_DONE. So the AMFD can not accept any node up event on remaining node.
+
In syslog
2019-06-13 14:06:27.023 SC-1 osafamfd[261]: NO Received node_up from 2020f:
msg_id 1
2019-06-13 14:06:27.024 SC-1 osafamfd[261]: NO Received node_up from 2040f:
msg_id 1
~~~~
---
** [tickets:#3051] amf: nodes can not join the cluster**
**Status:** assigned
**Milestone:** 5.19.06
**Created:** Fri Jun 14, 2019 12:54 AM UTC by Thang Duc Nguyen
**Last Updated:** Fri Jun 14, 2019 12:57 AM UTC
**Owner:** Thang Duc Nguyen
There is a situation, SC-1 sees SC-2 active then rde role on SC-1 changes to
QIESCED. Amfd on SC-1 has not assigned standby yet. At that time active SC-2 is
rebooted. The SI of Nored Opensaf app was assgned on SC-1 successfully on SC-1
but the SU-SI record not created by amfd.
After SC-1 is promoted to ACTIVE but init_state of amfd can not move to
AVD_INIT_DONE. So the AMFD can not accept any node up event on remaining node.
In syslog
2019-06-13 14:06:27.023 SC-1 osafamfd[261]: NO Received node_up from 2020f:
msg_id 1
2019-06-13 14:06:27.024 SC-1 osafamfd[261]: NO Received node_up from 2040f:
msg_id 1
2019-06-13 14:06:28.031 SC-1 osafamfd[261]: NO Received node_up from 2050f:
msg_id 1
2019-06-13 14:06:28.037 SC-1 osafamfd[261]: NO Received node_up from 2030f:
msg_id 1
2019-06-13 14:06:28.123 SC-1 osafamfd[261]: NO Received node_up from 2020f:
msg_id 1
2019-06-13 14:06:28.125 SC-1 osafamfd[261]: NO Received node_up from 2040f:
msg_id 1
2019-06-13 14:06:29.123 SC-1 osafamfd[261]: NO Received node_up from 2050f:
msg_id 1
2019-06-13 14:06:29.123 SC-1 osafamfd[261]: NO Received node_up from 2030f:
msg_id 1
2019-06-13 14:06:29.229 SC-1 osafamfd[261]: NO Received node_up from 2040f:
msg_id 1
2019-06-13 14:06:29.240 SC-1 osafamfd[261]: NO Received node_up from 2020f:
msg_id 1
2019-06-13 14:06:30.223 SC-1 osafamfd[261]: NO Received node_up from 2050f:
msg_id 1
2019-06-13 14:06:30.223 SC-1 osafamfd[261]: NO Received node_up from 2030f:
msg_id 1
2019-06-13 14:06:30.340 SC-1 osafamfd[261]: NO Received node_up from 2040f:
msg_id 1
2019-06-13 14:06:30.342 SC-1 osafamfd[261]: NO Received node_up from 2020f:
msg_id 1
---
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