Re: [ClusterLabs] start vs promote drbd m/s colocation constraint

2021-02-02 Thread Brent Jensen
On 2/2/2021 4:02 PM, Ken Gaillot wrote: I haven't used DRBD in a while, but I believe newer versions handle the equivalent of promotion internally, rather than via the resource agent and pacemaker. It could be that you simply don't need a promotable clone, just a regular clone. I don't know how

Re: [ClusterLabs] start vs promote drbd m/s colocation constraint

2021-02-02 Thread Ken Gaillot
On Tue, 2021-02-02 at 14:27 -0700, Brent Jensen wrote: > I've been trying to get my DRBD cluster on Centos8 / Pacemaker 2 to > work but have had issues with cluster not failing over (I get error > messages like "Refusing to be Primary while peer is not outdated"). > This has been explained in

[ClusterLabs] pcs status command output consist of * in each line , is this expected behavior

2021-02-02 Thread S Sathish S
Hi Team, we have taken latest pacemaker version after that we found pcs status command output consist of * in each line , is this expected behavior. https://github.com/ClusterLabs/pacemaker/tree/Pacemaker-2.0.5 pcs status command output : Cluster name: TEST Cluster Summary: * Stack:

[ClusterLabs] start vs promote drbd m/s colocation constraint

2021-02-02 Thread Brent Jensen
I've been trying to get my DRBD cluster on Centos8 / Pacemaker 2 to work but have had issues with cluster not failing over (I get error messages like "Refusing to be Primary while peer is not outdated"). This has been explained in other posts. In trying different things I changed my constraint

Re: [ClusterLabs] pcs status command output consist of * in each line , is this expected behavior

2021-02-02 Thread Ken Gaillot
On Tue, 2021-02-02 at 06:20 +, S Sathish S wrote: > Hi Team, > > we have taken latest pacemaker version after that we found pcs status > command output consist of * in each line , is this expected behavior. Yes, this is a fairly recent change, part of an ongoing project to make Pacemaker's

Re: [ClusterLabs] pcs status command output consist of * in each line , is this expected behavior

2021-02-02 Thread Reid Wahl
Looks like it. https://github.com/ClusterLabs/pacemaker/blob/Pacemaker-2.0.5/tools/crm_mon_curses.c#L295-L301 On Tue, Feb 2, 2021 at 9:36 AM S Sathish S wrote: > Hi Team, > > > > we have taken latest pacemaker version after that we found pcs status > command output consist of * in each line ,

Re: [ClusterLabs] Anyone using remote-clear-port or remote-tls-port for remote CIB administration?

2021-02-02 Thread Ken Gaillot
On Tue, 2021-02-02 at 16:58 +, Walker, Chris wrote: > Yes, we use remote-tls-port for remote admin commands. Perhaps we > should be looking into other options? > Thanks, > Chris No, as long as people find it useful we'll keep it. > From: Users > Date: Tuesday, February 2, 2021 at 11:41 AM

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

2021-02-02 Thread Stuart Massey
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

Re: [ClusterLabs] Anyone using remote-clear-port or remote-tls-port for remote CIB administration?

2021-02-02 Thread Walker, Chris
Yes, we use remote-tls-port for remote admin commands. Perhaps we should be looking into other options? Thanks, Chris From: Users Date: Tuesday, February 2, 2021 at 11:41 AM To: Cluster Labs - All topics related to open-source clustering welcomed Subject: [ClusterLabs] Anyone using

[ClusterLabs] Anyone using remote-clear-port or remote-tls-port for remote CIB administration?

2021-02-02 Thread Ken Gaillot
Hi all, Pacemaker has a feature allowing CIB modifications to be made from hosts that are not cluster nodes: https://clusterlabs.org/pacemaker/doc/en-US/Pacemaker/2.0/html-single/Pacemaker_Administration/#s-remote-connection Does anyone actually use this? If it is being used, I have no problem

Re: [ClusterLabs] CVE-2020-11078 vulnerable to resource-agents module

2021-02-02 Thread Oyvind Albrigtsen
There is no fix for this in the agents, so you just need to check that you're using httplib2 v0.18.0 or later, or that your distros httplib2 package changelog mentions that the CVE has been fixed to ensure you wont be vulnerable.

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

2021-02-02 Thread Stuart Massey
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

[ClusterLabs] pcs 0.10.8 released

2021-02-02 Thread Tomas Jelinek
I am happy to announce the latest release of pcs, version 0.10.8. Source code is available at: https://github.com/ClusterLabs/pcs/archive/0.10.8.tar.gz or https://github.com/ClusterLabs/pcs/archive/0.10.8.zip This release brings new commands for modifying corosync configuration in an existing