[ClusterLabs] Antw: [EXT] Re: Peer (slave) node deleting master's transient_attributes

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

[ClusterLabs] Antw: [EXT] Re: node fencing due to "Stonith/shutdown of node .. was not expected" while the node shut down cleanly

>>> Ken Gaillot schrieb am 08.02.2021 um 17:43 in Nachricht <5ee981d3893dd7712c747661de05240df1ccd8eb.ca...@redhat.com>: > On Mon, 2021‑02‑08 at 08:41 +0100, Ulrich Windl wrote: >> Hi! >> >> There were previous indications of this problem, but today I had it >> again: >> I restarted a node (h18,

Re: [ClusterLabs] Peer (slave) node deleting master's transient_attributes

Wonderful, thank you for looking at this! I have posted uncompressed "saving inputs" files at the links below - 3241 is the immediately preceding one that exists, and 3242 is the one created upon encountering the problem state. In both cases, it looks to me like node02 is DC. There are none of thes

Re: [ClusterLabs] Peer (slave) node deleting master's transient_attributes

On Mon, 2021-02-08 at 12:01 -0500, Stuart Massey wrote: > I'm wondering if anyone can advise us on next steps here and/or > correct our understanding. This seems like a race condition that > causes resources to be stopped unnecessarily. Is there a way to > prevent a node from processing cib updates

Re: [ClusterLabs] Peer (slave) node deleting master's transient_attributes

I'm wondering if anyone can advise us on next steps here and/or correct our understanding. This seems like a race condition that causes resources to be stopped unnecessarily. Is there a way to prevent a node from processing cib updates from a peer while DC negotiations are underway? Our "node02" is

Re: [ClusterLabs] node fencing due to "Stonith/shutdown of node .. was not expected" while the node shut down cleanly

On Mon, 2021-02-08 at 08:41 +0100, Ulrich Windl wrote: > Hi! > > There were previous indications of this problem, but today I had it > again: > I restarted a node (h18, DC) via "crm cluster restart", and the node > shutdown cleanly (at least it came to an end), but when restarting, > the node was

Re: [ClusterLabs] Old pcs-0.9.167/0.9.168/0.9.169 package with newer corosync-3.1 and pacemaker-2.1 on RHEL 7.7

Due to the concerns already mentioned, it is much easier to stick with Corosync 2 + Pacemaker 1 on RHEL 7, but I will mention that the particular issue in the original message should be resolved if Pacemaker 2 is built with ./configure --enable-legacy-links. However pcs 0.9 would still only be part

Re: [ClusterLabs] Antw: Re: Antw: [EXT] Re: Q: starting systemd resources

On Mon, 2021-02-08 at 09:30 +0100, Ulrich Windl wrote: > > > > Ken Gaillot schrieb am 05.02.2021 um > > > > 16:47 in Nachricht > > <7247097610e6ab4f3a44a7648e0acf32fbdb9937.ca...@redhat.com>: > > Hi! > > ... > > > Doesn't systemctl return a proper exit status? > > > > It does, but we don't use

Re: [ClusterLabs] Old pcs-0.9.167/0.9.168/0.9.169 package with newer corosync-3.1 and pacemaker-2.1 on RHEL 7.7

Hi Fabio, Thank You for your answer! BR, Szabi. ___ Szabolcs-Gavril Rugina Development Information Technologies 1  / Software Engineer FREQUENTIS ROMÂNIA SRL Str. Taietura Turcului, Nr.  47, 400221, Cluj-Napoca, Romania Phone   +43-1-81150-7511

Re: [ClusterLabs] Pacemaker 1.1 support period

Hello Ken, Thank you for reply. Best Regards, Andrei Andrei Zheregelia| Senior Software Engineer| DSR Corporation | E-mail: andrei.zherege...@dsr-corporation.com DSR logo

Re: [ClusterLabs] fence-agents v4.7.1

Correction: bugfix release for v4.7.0. On 08/02/21 12:01 +0100, Oyvind Albrigtsen wrote: ClusterLabs is happy to announce fence-agents v4.7.1, which is a bugfix release for v4.7.1. The source code is available at: https://github.com/ClusterLabs/fence-agents/releases/tag/v4.7.1 The most signifi

[ClusterLabs] fence-agents v4.7.1

ClusterLabs is happy to announce fence-agents v4.7.1, which is a bugfix release for v4.7.1. The source code is available at: https://github.com/ClusterLabs/fence-agents/releases/tag/v4.7.1 The most significant enhancements in this release are: - bugfixes and enhancements: - fence_aws/fence_gce:

Re: [ClusterLabs] Old pcs-0.9.167/0.9.168/0.9.169 package with newer corosync-3.1 and pacemaker-2.1 on RHEL 7.7

Hi, There are significant changes between corosync 2.x and 3.x and similarly between pacemaker 1.x and 2.x. To cover those and support the new versions, we created pcs-0.10 branch. The old versions are supported by pcs-0.9 branch. RHEL 7 ships corosync 2.x and pacemaker 1.x, so we build pcs-

[ClusterLabs] Antw: Re: Antw: [EXT] Re: Q: starting systemd resources

>>> Ken Gaillot schrieb am 05.02.2021 um 16:47 in >>> Nachricht <7247097610e6ab4f3a44a7648e0acf32fbdb9937.ca...@redhat.com>: Hi! ... >> Doesn't systemctl return a proper exit status? > > It does, but we don't use systemctl, we use the systemd C library > interface. And unfortunately, our curre

[ClusterLabs] Antw: Re: Antw: [EXT] Re: failed migration handled the wrong way

>>> Andrei Borzenkov schrieb am 05.02.2021 um 15:31 in Nachricht <4572fad7-c5ae-6d93-2559-741d052e3...@gmail.com>: > 05.02.2021 12:54, Ulrich Windl пишет: > Ulrich Windl schrieb am 01.02.2021 um 11:59 in Nachricht <6017DF04.888 : >> 161 : >> 60728>: >> Andrei Borzenkov schrieb am 01.02.20