On Thu, Mar 24, 2022 at 4:12 PM Ken Gaillot wrote:
>
> On Wed, 2022-03-23 at 05:30 +, Balotra, Priyanka wrote:
> > Hi All,
> >
> > We have a scenario on SLES 12 SP3 cluster.
> > The scenario is explained as follows in the order of events:
> > There is a 2-node cluster (FILE-1, FILE-2)
> >
On Wed, 2022-03-23 at 05:30 +, Balotra, Priyanka wrote:
> Hi All,
>
> We have a scenario on SLES 12 SP3 cluster.
> The scenario is explained as follows in the order of events:
> There is a 2-node cluster (FILE-1, FILE-2)
> The cluster and the resources were up and running fine initially .
On 23.03.2022 08:30, Balotra, Priyanka wrote:
> Hi All,
>
> We have a scenario on SLES 12 SP3 cluster.
> The scenario is explained as follows in the order of events:
>
> * There is a 2-node cluster (FILE-1, FILE-2)
> * The cluster and the resources were up and running fine initially .
>
Hi All,
We have a scenario on SLES 12 SP3 cluster.
The scenario is explained as follows in the order of events:
- There is a 2-node cluster (FILE-1, FILE-2)
- The cluster and the resources were up and running fine initially .
- Then fencing request from pacemaker got
Hi All,
We have a scenario on SLES 12 SP3 cluster.
The scenario is explained as follows in the order of events:
* There is a 2-node cluster (FILE-1, FILE-2)
* The cluster and the resources were up and running fine initially .
* Then fencing request from pacemaker got issued on both
