Sent: Thursday, August 18, 2022 21:26
To: users@clusterlabs.org
Subject: Re: [ClusterLabs] Start resource only if another resource is
stopped
On 17.08.2022 16:58, Miro Igov wrote:
> As you guessed i am using crm res stop nfs_export_1.
> I tried the solution with attribute and it does no
On Thu, Aug 18, 2022 at 8:26 PM Andrei Borzenkov wrote:
>
> On 17.08.2022 16:58, Miro Igov wrote:
> > As you guessed i am using crm res stop nfs_export_1.
> > I tried the solution with attribute and it does not work correct.
> >
>
> It does what you asked for originally, but you are shifting the
>
On 17.08.2022 16:58, Miro Igov wrote:
> As you guessed i am using crm res stop nfs_export_1.
> I tried the solution with attribute and it does not work correct.
>
It does what you asked for originally, but you are shifting the
goalposts ...
> When i stop nfs_export_1 it stops data_1 data_1_acti
As you guessed i am using crm res stop nfs_export_1.
I tried the solution with attribute and it does not work correct.
When i stop nfs_export_1 it stops data_1 data_1_active, then it starts
data_2_failover - so far so good.
When i start nfs_export_1 it starts data_1, starts data_1_active and the
On 11.08.2022 17:34, Miro Igov wrote:
> Hello,
>
> I am trying to create failover resource that would start if another resource
> is stopped and stop when the resource is started back.
>
> It is 4 node cluster (with qdevice) where nodes are virtual machines and two
> of them are hosted in a datac
Hello,
I am trying to create failover resource that would start if another resource
is stopped and stop when the resource is started back.
It is 4 node cluster (with qdevice) where nodes are virtual machines and two
of them are hosted in a datacenter and the other 2 VMs in another
datacenter.
Na
