Re: [ClusterLabs] Resource Parameter Change Not Honoring Constraints

On Wed, Apr 1, 2020 at 8:01 PM Ken Gaillot wrote: > > On Thu, 2020-03-19 at 13:39 -0400, Marc Smith wrote: > > On Mon, Mar 16, 2020 at 1:26 PM Marc Smith > > wrote: > > > > > > On Thu, Mar 12, 2020 at 10:51 AM Ken Gaillot > > > wrote: > >

Re: [ClusterLabs] Resource Parameter Change Not Honoring Constraints

On Mon, Mar 16, 2020 at 1:26 PM Marc Smith wrote: > > On Thu, Mar 12, 2020 at 10:51 AM Ken Gaillot wrote: > > > > On Wed, 2020-03-11 at 17:24 -0400, Marc Smith wrote: > > > Hi, > > > > > > I'm using Pacemaker 1.1.20 (yes, I know, a bit dated now). I n

Re: [ClusterLabs] Resource Parameter Change Not Honoring Constraints

On Thu, Mar 12, 2020 at 10:51 AM Ken Gaillot wrote: > > On Wed, 2020-03-11 at 17:24 -0400, Marc Smith wrote: > > Hi, > > > > I'm using Pacemaker 1.1.20 (yes, I know, a bit dated now). I noticed > > I'd still consider that recent :) > > > when I modify a r

[ClusterLabs] Resource Parameter Change Not Honoring Constraints

Hi, I'm using Pacemaker 1.1.20 (yes, I know, a bit dated now). I noticed when I modify a resource parameter (eg, update the value), this causes the resource itself to restart. And that's fine, but when this resource is restarted, it doesn't appear to honor the full set of constraints for that

[ClusterLabs] SBD Watchdog Question

Hi, I'm testing a two-node cluster using SBD 1.4.0, Corosync 2.4.2, and Pacemaker 1.1.16. For testing, I have one shared block storage device between the two nodes, and each node has an "IPMI watchdog" device available at '/dev/watchdog'. Up until today, I've been testing the SBD fencing

[ClusterLabs] Colocation by Node

Hi, I'm looking for the correct constraint setup to use for the following resource configuration: --snip-- node 1: tgtnode2.parodyne.com node 2: tgtnode1.parodyne.com primitive p_iscsi_tgtnode1 iscsi \ params portal=172.16.0.12 target=tgtnode2_redirect udev=no try_recovery=true \

[ClusterLabs] Resource Demote Time Out Question

Hi, I'm experiencing a time out on a demote operation and I'm not sure which parameter / attribute needs to be updated to extend the time out window. I'm using Pacemaker 1.1.16 and Corosync 2.4.2. Here are the set of log lines that show the issue (shutdown initiated, then demote time out after

Re: [ClusterLabs] ocf:lvm2:VolumeGroup Probe Issue

Perfect, thanks for the quick reply. --Marc On Tue, Nov 8, 2016 at 12:00 PM, Ken Gaillot <kgail...@redhat.com> wrote: > On 11/08/2016 10:37 AM, Marc Smith wrote: >> Hi, >> >> First, I realize ocf:lvm2:VolumeGroup comes from the LVM2 package and >> not resour

[ClusterLabs] ocf:lvm2:VolumeGroup Probe Issue

Hi, First, I realize ocf:lvm2:VolumeGroup comes from the LVM2 package and not resource-agents, but I'm hoping someone on this list is familiar with this RA and can provide some insight. In my cluster configuration, I'm using ocf:lvm2:VolumeGroup to manage my LVM VG's, and I'm using the cluster

Re: [ClusterLabs] crmsh Question/Feature

Thanks; I've submitted the pull request. --Marc On Mon, Jan 25, 2016 at 1:30 AM, Kristoffer Grönlund <kgronl...@suse.com> wrote: > Hi, > > Marc Smith <marc.sm...@mcc.edu> writes: > >> I think "push" fits. I haven't contributed to this project befo

Re: [ClusterLabs] crmsh Question/Feature

On Thu, Jan 21, 2016 at 12:39 AM, Kristoffer Grönlund <kgronl...@suse.com> wrote: > Hi, > > Marc Smith <marc.sm...@mcc.edu> writes: > >> My question: Is there any other way to replicate this behavior using >> crmsh and importing a configuration from a file

[ClusterLabs] crmsh Question/Feature

Hi, First a description of what I'd like to accomplish: - I'm using crmsh to retrieve a cluster configuration by using "crm configure save /tmp/file". - I am then reading the bytes from the '/tmp/file' into a string that I'm modifying elsewhere. - I remove some lines from that cluster