On Fri, 2023-06-09 at 14:03 +0200, Ondrej Mular wrote:
> To me, this seems like an issue in `crm_resource` as the error
> message
> comes from it. Pcs is actually using `crm_resource --move` when
> moving
> resources. In this case, pcs should call `crm_resource --move
> REDIS-clone --node podnode3
To me, this seems like an issue in `crm_resource` as the error message
comes from it. Pcs is actually using `crm_resource --move` when moving
resources. In this case, pcs should call `crm_resource --move
REDIS-clone --node podnode3 --master`, you can see that if you run pcs
with `--debug` option.
On 09/06/2023 09:04, Reid Wahl wrote:
On Thu, Jun 8, 2023 at 10:55 PM lejeczek via Users
wrote:
On 09/06/2023 01:38, Reid Wahl wrote:
On Thu, Jun 8, 2023 at 2:24 PM lejeczek via Users wrote:
Ouch.
Let's see the full output of the move command, with the whole CIB that
failed to
On Thu, Jun 8, 2023 at 10:55 PM lejeczek via Users
wrote:
>
>
>
> On 09/06/2023 01:38, Reid Wahl wrote:
> > On Thu, Jun 8, 2023 at 2:24 PM lejeczek via Users
> > wrote:
> >>
> >>
> >>> Ouch.
> >>>
> >>> Let's see the full output of the move command, with the whole CIB that
> >>> failed to
On 09/06/2023 01:38, Reid Wahl wrote:
On Thu, Jun 8, 2023 at 2:24 PM lejeczek via Users wrote:
Ouch.
Let's see the full output of the move command, with the whole CIB that
failed to validate.
For a while there I thought perhaps it was just that one
pglsq resource, but it seems that any
On Thu, Jun 8, 2023 at 2:24 PM lejeczek via Users wrote:
>
>
>
> > Ouch.
> >
> > Let's see the full output of the move command, with the whole CIB that
> > failed to validate.
> >
> For a while there I thought perhaps it was just that one
> pglsq resource, but it seems that any - though only a
Ouch.
Let's see the full output of the move command, with the whole CIB that
failed to validate.
For a while there I thought perhaps it was just that one
pglsq resource, but it seems that any - though only a few
are set up - (only clone promoted?)resource fails to move.
Perhaps primarily
On Tue, Jun 6, 2023 at 2:34 AM lejeczek via Users wrote:
>
>
>
> On 05/06/2023 16:23, Ken Gaillot wrote:
> > On Sat, 2023-06-03 at 15:09 +0200, lejeczek via Users wrote:
> >> Hi guys.
> >>
> >> I've something which I'm new to entirely - cluster which is seemingly
> >> okey errors, fails to move a
On 05/06/2023 16:23, Ken Gaillot wrote:
On Sat, 2023-06-03 at 15:09 +0200, lejeczek via Users wrote:
Hi guys.
I've something which I'm new to entirely - cluster which is seemingly
okey errors, fails to move a resource.
What pcs version are you using? I believe there was a move regression
On 05/06/2023 16:23, Ken Gaillot wrote:
On Sat, 2023-06-03 at 15:09 +0200, lejeczek via Users wrote:
Hi guys.
I've something which I'm new to entirely - cluster which is seemingly
okey errors, fails to move a resource.
What pcs version are you using? I believe there was a move regression
On Sat, 2023-06-03 at 15:09 +0200, lejeczek via Users wrote:
> Hi guys.
>
> I've something which I'm new to entirely - cluster which is seemingly
> okey errors, fails to move a resource.
What pcs version are you using? I believe there was a move regression
in a recent push.
> I'd won't
Hi guys.
I've something which I'm new to entirely - cluster which is
seemingly okey errors, fails to move a resource.
I'd won't contaminate here just yet with long json cluster
spits when fails but a snippet:
-> $ pcs resource move PGSQL-clone --promoted podnode1
Error: cannot move resource
12 matches
Mail list logo
