Analysis:
In case of failover, fm reboots its own node if csi is not assigned to
it(csi_assigned is false) by Amf. In this scenario, while standby controller is
coming up, Act Amfd has send SUSI to upcoming node Amfnd and Amfnd has assigned
the role to fmd.
Apr 22 21:02:34 CONTROLLER-2 osafamfnd[5620]: NO Assigning
'safSi=SC-2N,safApp=OpenSAF' STANDBY to 'safSu=SC-2,safSg=2N,safApp=OpenSAF'
Apr 22 21:02:34 CONTROLLER-2 osafamfnd[5620]: NO Assigned
'safSi=SC-2N,safApp=OpenSAF' STANDBY to 'safSu=SC-2,safSg=2N,safApp=OpenSAF'
But, Standby Amfd is yet to complete the cold sync and node failover happend.
Amf can provide a reboot in this case if fms don't care to handle it.
Suggestion ??
Thanks
-Nagu
---
** [tickets:#1334] OUT_OF_SYNC (failed over) new active controller should go
for immediate reboot**
**Status:** unassigned
**Milestone:** 4.4.2
**Created:** Wed Apr 22, 2015 04:42 PM UTC by Srikanth R
**Last Updated:** Thu Apr 23, 2015 06:18 AM UTC
**Owner:** nobody
Changeset : 6377
Issue : Out of sync (failed over) new active controller should go for immediate
reboot
During failover, if the standby controller is OUT OF SYNC and could not get
promoted to active, amfnd should reboot the node immediately. The node went for
reboot after 180 seconds or so. In this scenario, cold sync could not be
completed.Hence Out of sync.
Apr 22 21:02:45 CONTROLLER-2 osaffmd[5534]: NO Current role: STANDBY
Apr 22 21:02:45 CONTROLLER-2 osaffmd[5534]: Rebooting OpenSAF NodeId = 131343
EE Name = ,
Apr 22 21:02:45 CONTROLLER-2 osaffmd[5534]: NO Controller Failover: Setting
role to ACTIVE
Apr 22 21:02:45 CONTROLLER-2 osafrded[5525]: NO RDE role set to ACTIVE
Apr 22 21:02:45 CONTROLLER-2 osafamfd[5610]: NO FAILOVER StandBy --> Active
Apr 22 21:02:45 CONTROLLER-2 osafamfd[5610]: ER FAILOVER StandBy --> Active
FAILED, Standby OUT OF SYNC
Apr 22 21:02:45 CONTROLLER-2 osafamfd[5610]: ER avd_role_change role change
failure
Apr 22 21:05:43 CONTROLLER-2 osafamfnd[5620]: ER AMF director unexpectedly
crashed
Apr 22 21:05:43 CONTROLLER-2 osafamfnd[5620]: Rebooting OpenSAF NodeId = 131599
EE Name = , Reason: local AVD down(Adest) or both AVD down(Vdest) received,
OwnNodeId = 131599, SupervisionTime = 60
Apr 22 21:05:43 CONTROLLER-2 opensaf_reboot: Rebooting local node; timeout=60
In similar scenario, fmd process rebooted the node when it detected that the
standby is not ready to take active role.
Apr 22 21:58:10 CONTROLLER-1 osaffmd[5516]: Rebooting OpenSAF NodeId = 0 EE
Name = No EE Mapped, Reason: Failover occurred, but this node is not yet ready,
OwnNodeId = 131343, SupervisionTime = 60
---
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.------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
