On both controller there should be an interface for TCP/stonith, the
"backplane".
Otherwise there are no way to remote fence the other node. So this test case
has only verified the old behaviour, where split brain, in this case, is
detected by amfd that exits and amfnd order a reboot of the node.
---
** [tickets:#2097] Both controllers went for reboot while recovering from split
brain**
**Status:** unassigned
**Milestone:** 5.2.FC
**Created:** Thu Oct 06, 2016 04:58 AM UTC by Chani Srivastava
**Last Updated:** Thu Oct 06, 2016 12:10 PM UTC
**Owner:** nobody
**Attachments:**
-
[Fencing_logs.zip](https://sourceforge.net/p/opensaf/tickets/2097/attachment/Fencing_logs.zip)
(43.3 kB; application/zip)
S : Ubuntu 64bit
Changeset : 7997 ( 5.1.FC)
Setup : 3-node cluster (2 controllers, 1 payload) Remote fencing enabled
Steps:
1. Bring up OpenSaf on all nodes
2. Enable STONITH
3. Disconnect network from both controllers at the same time -- This will
stimulate split brain and both controllers become ACTIVE
4. Connect network to both controllers together --- Both controllers reboot
Expected: Controllers should join the cluster by rebooting only one of the
controller.
Syslog attached for both controllers
---
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
