On 06/09/2017 07:43 AM, ashutosh tiwari wrote:
> Hi,
>
> We have two node cluster(ACTIVE/STANDBY).
> Recently we moved these nodes to KVM.
>
> When we create a private virtual network and use this vnet for
> assigning cluster interfaces then things work as expected and both the
> nodes are able t
Hi,
We have two node cluster(ACTIVE/STANDBY).
Recently we moved these nodes to KVM.
When we create a private virtual network and use this vnet for assigning
cluster interfaces then things work as expected and both the nodes are able
to form the cluster.
Nodes are not able to form cluster when we
* Jean-Francois Malouin [20170607
13:09]:
> Hi,
..snip...
> I'm having some difficulties understanding the fencing_topology syntax.
> Making the changes adapted for my local configuration I get the error
> when trying to add the fence topology:
>
> ~# crm configure fencing_topology antonio: fe
Hi,
Looking at the incident around May 26 16:40:00, here is what happens:
You are setting the attribute for rhel73-2 from rhel73-1, while rhel73-2
is not part of cluster from rhel73-1's point of view.
The crm shell sets the node attribute for rhel73-2 with a CIB
modification that starts like thi