Ulrich,
Thank you for clarifying what single-node maintenance mode entails. It is
surprising to learn that, though resource actions do not happen, a node
would send a cib update that deletes the transient attributes that are
maintained by resource monitoring activities. I think "maintenance mode"
Hi!
Maybe you just misunderstand what maintennce mode for a single node means: CIBS
updates will still be performed, but not the resource actions. If CIB updates
are sent to another node, that node will perform actions.
Maybe just explain what you really want to do with one node in maintenance
A reasonable question from a practical on-the-ground perspective. Several
considerations contributed:
1. We need to induce the hardware errors to demonstrate the problem to
the hardware vendor, who is acting at their own pace. Leaving the node in
it's semi-active state seems to achieve
A reasonable question from a practical on-the-ground perspective. Several
considerations contributed:
1. We need to induce the hardware errors to demonstrate the problem to
the hardware vendor, who is acting at their own pace. Leaving the node in
it's semi-active state seems to achieve
>>> Ken Gaillot schrieb am 01.02.2021 um 17:27 in
Nachricht
<9b99d08faf4ddbe496ede10165f586afd81aa850.ca...@redhat.com>:
> On Mon, 2021-02-01 at 11:16 -0500, Stuart Massey wrote:
>> Andrei,
>> You are right, thank you. I have an earlier thread on which I posted
>> a pacemaker.log for this issue,
