[ClusterLabs] Problem with a ping resource on CentOS 8

fatcharly at gmx.de fatcharly at gmx.de
Fri Aug 27 11:33:03 EDT 2021


Hi,

I'm running a two node cluster on CentOS Linux release 8.4.2105 4.18.0-305.12.1.el8_4.x86_64 with the following pacemaker:
pacemaker-2.0.5-9.el8_4.1.x86_64
pacemaker-cluster-libs-2.0.5-9.el8_4.1.x86_64
pacemaker-libs-2.0.5-9.el8_4.1.x86_64
pacemaker-schemas-2.0.5-9.el8_4.1.noarch
pacemaker-cli-2.0.5-9.el8_4.1.x86_64

Both Nodes communicate with each other and the defined HA-IP's are working fine.
But when I add a ping-resource:

pcs resource create ping_fw ocf:pacemaker:ping dampen=5s multiplier=1000 host_list=192.168.20.1 clone

and a constraint location:

pcs constraint location HA-IP_211 rule score=-INFINITY ping_fw lt 1 or not_defined ping_fw

the cluster stops the HA-IP resources.

This is my configuration:

Cluster Name: loadbalancer
Corosync Nodes:
 pound31 pound32
Pacemaker Nodes:
 pound31 pound32

Resources:
 Resource: HA-IP_211 (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: cidr_netmask=24 ip=192.168.20.211
  Operations: monitor interval=15s (HA-IP_211-monitor-interval-15s)
              start interval=0s timeout=20s (HA-IP_211-start-interval-0s)
              stop interval=0s timeout=20s (HA-IP_211-stop-interval-0s)
 Resource: HA-IP_212 (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: cidr_netmask=24 ip=192.168.20.212
  Operations: monitor interval=15s (HA-IP_212-monitor-interval-15s)
              start interval=0s timeout=20s (HA-IP_212-start-interval-0s)
              stop interval=0s timeout=20s (HA-IP_212-stop-interval-0s)
 Resource: HA-IP_213 (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: cidr_netmask=24 ip=192.168.20.213
  Operations: monitor interval=15s (HA-IP_213-monitor-interval-15s)
              start interval=0s timeout=20s (HA-IP_213-start-interval-0s)
              stop interval=0s timeout=20s (HA-IP_213-stop-interval-0s)
 Resource: HA-IP_214 (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: cidr_netmask=24 ip=192.168.20.214
  Operations: monitor interval=15s (HA-IP_214-monitor-interval-15s)
              start interval=0s timeout=20s (HA-IP_214-start-interval-0s)
              stop interval=0s timeout=20s (HA-IP_214-stop-interval-0s)
 Resource: HA-IP_215 (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: cidr_netmask=24 ip=192.168.20.215
  Operations: monitor interval=15s (HA-IP_215-monitor-interval-15s)
              start interval=0s timeout=20s (HA-IP_215-start-interval-0s)
              stop interval=0s timeout=20s (HA-IP_215-stop-interval-0s)
 Resource: HA-IP_216 (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: cidr_netmask=24 ip=192.168.20.216
  Operations: monitor interval=15s (HA-IP_216-monitor-interval-15s)
              start interval=0s timeout=20s (HA-IP_216-start-interval-0s)
              stop interval=0s timeout=20s (HA-IP_216-stop-interval-0s)
 Resource: HA-IP_217 (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: cidr_netmask=24 ip=192.168.20.217
  Operations: monitor interval=15s (HA-IP_217-monitor-interval-15s)
              start interval=0s timeout=20s (HA-IP_217-start-interval-0s)
              stop interval=0s timeout=20s (HA-IP_217-stop-interval-0s)
 Resource: HA-IP_218 (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: cidr_netmask=24 ip=192.168.20.218
  Operations: monitor interval=15s (HA-IP_218-monitor-interval-15s)
              start interval=0s timeout=20s (HA-IP_218-start-interval-0s)
              stop interval=0s timeout=20s (HA-IP_218-stop-interval-0s)
 Resource: HA-IP_219 (class=ocf provider=heartbeat type=IPaddr2)
  Attributes: cidr_netmask=24 ip=192.168.20.219
  Operations: monitor interval=15s (HA-IP_219-monitor-interval-15s)
              start interval=0s timeout=20s (HA-IP_219-start-interval-0s)
              stop interval=0s timeout=20s (HA-IP_219-stop-interval-0s)
 Clone: ping_fw-clone
  Resource: ping_fw (class=ocf provider=pacemaker type=ping)
   Attributes: dampen=5s host_list=192.168.20.1 multiplier=1000
   Operations: monitor interval=10s timeout=60s (ping_fw-monitor-interval-10s)
               start interval=0s timeout=60s (ping_fw-start-interval-0s)
               stop interval=0s timeout=20s (ping_fw-stop-interval-0s)

Stonith Devices:
Fencing Levels:

Location Constraints:
  Resource: HA-IP_211
    Constraint: location-HA-IP_211
      Rule: boolean-op=or score=-INFINITY (id:location-HA-IP_211-rule)
        Expression: ping_fw lt 1 (id:location-HA-IP_211-rule-expr)
        Expression: not_defined ping_fw (id:location-HA-IP_211-rule-expr-1)
Ordering Constraints:
Colocation Constraints:
  HA-IP_212 with HA-IP_211 (score:INFINITY) (id:colocation-HA-IP_212-HA-IP_211-INFINITY)
  HA-IP_213 with HA-IP_211 (score:INFINITY) (id:colocation-HA-IP_213-HA-IP_211-INFINITY)
  HA-IP_214 with HA-IP_211 (score:INFINITY) (id:colocation-HA-IP_214-HA-IP_211-INFINITY)
  HA-IP_215 with HA-IP_211 (score:INFINITY) (id:colocation-HA-IP_215-HA-IP_211-INFINITY)
  HA-IP_216 with HA-IP_211 (score:INFINITY) (id:colocation-HA-IP_216-HA-IP_211-INFINITY)
  HA-IP_217 with HA-IP_211 (score:INFINITY) (id:colocation-HA-IP_217-HA-IP_211-INFINITY)
  HA-IP_218 with HA-IP_211 (score:INFINITY) (id:colocation-HA-IP_218-HA-IP_211-INFINITY)
  HA-IP_219 with HA-IP_211 (score:INFINITY) (id:colocation-HA-IP_219-HA-IP_211-INFINITY)
Ticket Constraints:

Alerts:
 No alerts defined

Resources Defaults:
  No defaults set
Operations Defaults:
  No defaults set

Cluster Properties:
 cluster-infrastructure: corosync
 cluster-name: loadbalancer
 dc-version: 2.0.5-9.el8_4.1-ba59be7122
 have-watchdog: false
 stonith-enabled: false

Tags:
 No tags defined

Quorum:
  Options:


Any suggestions are welcome

Best regards and stay safe

fatcharly




More information about the Users mailing list