On 4/20/21 11:43 PM, Ken Gaillot wrote:
On Tue, 2021-04-20 at 13:43 -0700, Matthew Schumacher wrote:
I have a resource that more or less makes or breaks everything
(storage).
When I move it, it only takes a few seconds and everything keeps
working
due to timeouts, however, if another resource t
>>> Matthew Schumacher schrieb am 20.04.2021 um 22:43 in
Nachricht :
> I have a resource that more or less makes or breaks everything (storage).
>
> When I move it, it only takes a few seconds and everything keeps working
> due to timeouts, however, if another resource tries to migrate/move at
Hi!
I thought this problem was fixed upstream, but I wonder for SLES15 SP2
(crmsh-4.3.0+20210315.5d07d43e-5.45.1.noarch, Build Date : Tue Apr 6 12:06:38
2021):
crm(live/h16)configure# edit prm_xen ## After saving
ERROR: prm_xen: parameter "param" is not known
Traceback (most recent call last):
On 4/21/21 12:48 AM, Klaus Wenninger wrote:
Just to better understand the issue ...
Does the first resource implement storage that is being used
by the resource that is being migrated/moved?
Or is it just the combination of 2 parallel moves that is
overcommitting storage or network?
Is it assured
On 21.04.2021 19:27, Matthew Schumacher wrote:
> On 4/21/21 12:48 AM, Klaus Wenninger wrote:
>> Just to better understand the issue ...
>> Does the first resource implement storage that is being used
>> by the resource that is being migrated/moved?
>> Or is it just the combination of 2 parallel mov
On 4/21/21 10:21 AM, Andrei Borzenkov wrote:
If I set the stickiness to 100 then it's a race condition, many times we
get the storage layer migrated without VirtualDomain noticing, but if
the stickiness is not set, then moving a resource causes the cluster to
re-balance and will cause the VM to f
Hi Ulrich,
May I take a look at your output of `crm configure show` before crash?
Thanks!
From: Users on behalf of Ulrich Windl
Sent: Wednesday, April 21, 2021 6:53 PM
To: users@clusterlabs.org
Subject: [ClusterLabs] SLES15 crm shell crash "ERROR: ...: parame
