Pacemaker 1.1.22 - Release Candidate 1

This is a maintenance release with selected backports from the 2.0.3-rc1 release.

• Features added since Pacemaker-1.1.21

  • crmd: new 'fence-reaction' cluster option specifies whether local node should 'stop' or 'panic' if notified of own fencing
  • Pacemaker Remote: allow file for environment variables when used in bundle
  • Pacemaker Remote: allow configurable listen address and TLS priorities
  • tools: crm_simulate --repeat option to repeat profiling tests
  • tools: new pcmk_simtimes tool to compare crm_simulate profiling output

• Changes since Pacemaker-1.1.21

  • fencing: do not block concurrent fencing actions on a device (regression since 1.1.21)
  • crmd: set timeout on scheduler responses to avoid infinite wait
  • crmd: confirm cancel of failed monitors, to avoid transition timeout
  • lrmd: let controller cancel monitors, to avoid transition timeout
  • lrmd: return error for stonith probes if stonith connection was lost
  • fencing: ensure concurrent fencing commands always get triggered to execute
  • fencing: fail pending actions and re-sync history after crash and restart
  • fencing: don't let command with long delay block other pending commands
  • fencing: allow functioning even if CIB updates arrive unceasingly
  • pengine: calculate secure digests for unfencing, for replaying saved CIBs
  • pengine: properly detect dangling migrations, to avoid restart loop
  • pengine: avoid delay in recovery of failed remote connections
  • pengine: avoid scheduling actions on remote node that is shutting down
  • pengine: wait for probe actions to complete to prevent unnecessary restart/re-promote of dependent resources
  • libcrmcommon: avoid possible use-of-NULL when applying XML diffs
  • libcrmcommon: correctly apply XML diffs with multiple move/create changes
  • libcrmcommon: return error when applying XML diffs containing unknown operations
  • tools: fail if tar is not available when running crm_report
  • tools: correct crm_report argument parsing
  • tools: crm_report: don't ignore log if unrelated file is too large
  • agents: calculate #health_disk correctly in SysInfo
  • agents: handle run-as-user properly in ClusterMon

Pacemaker 2.0.3 - Release Candidate 1

• Features added since Pacemaker-2.0.2

  • controller: new 'fence-reaction' cluster option specifies whether local node
    should 'stop' or 'panic' if notified of own fencing
  • controller: allow more cluster properties to take ISO 8601 specification
  • controller: calculate cluster recheck interval dynamically when possible
  • Pacemaker Remote: allow file for environment variables when used in bundle
  • Pacemaker Remote: allow configurable listen address and TLS priorities
  • tools: crm_mon now supports standard --output-as/--output-to options
  • tools: crm_mon HTML output supports user-defined title and CSS stylesheet
  • tools: stonith_admin now supports HTML output in addition to text and XML
  • tools: crm_simulate --repeat option to repeat profiling tests
  • tools: new pcmk_simtimes tool to compare crm_simulate profiling output

• Changes since Pacemaker-2.0.2

  • fencer: do not block concurrent fencing actions on a device
    (regression since 2.0.2)
  • all: avoid Year 2038 issues
  • all: allow ISO 8601 strings of form "<date>T<time> <offset>"
  • controller: set timeout on scheduler responses to avoid infinite wait
  • controller: confirm cancel of failed monitors, to avoid transition timeout
  • executor: let controller cancel monitors, to avoid transition timeout
  • executor: return error for stonith probes if stonith connection was lost
  • fencer: ensure concurrent fencing commands always get triggered to execute
  • fencer: fail pending actions and re-sync history after crash and restart
  • fencer: don't let command with long delay block other pending commands
  • fencer: allow functioning even if CIB updates arrive unceasingly
  • scheduler: calculate secure digests for unfencing, for replaying saved CIBs
  • scheduler: properly detect dangling migrations, to avoid restart loop
  • scheduler: avoid delay in recovery of failed remote connections
  • scheduler: avoid scheduling actions on remote node that is shutting down
  • scheduler: wait for probe actions to complete to prevent unnecessary
    restart/re-promote of dependent resources
  • libcrmcommon: avoid possible use-of-NULL when applying XML diffs
  • libcrmcommon: correctly apply XML diffs with multiple move/create changes
  • libcrmcommon: return error when applying XML diffs with unknown operations
  • tools: avoid duplicate lines between nodes in crm_simulate dot graph
  • tools: organize crm_mon text output with list headings, indents, bullets
  • tools: fail if tar is not available when running crm_report
  • tools: correct crm_report argument parsing
  • tools: crm_report: don't ignore log if unrelated file is too large
  • tools: stonith_admin --list-targets should show what fencer would use
  • agents: calculate #health_disk correctly in SysInfo
  • agents: handle run-as-user properly in ClusterMon
  • agents: SysInfo support for K, T, and P units in addition to Kb and G

Pacemaker-2.0.2

Known regressions introduced in this release

• Concurrent fence actions on a single device could be incorrectly blocked (fixed in 2.0.3)

Features added since Pacemaker-2.0.1

• tools: crm_resource --validate can get resource parameters from command line
• tools: crm_resource --clear prints out any cleared constraints
• tools: new crm_rule tool for checking rule expiration (experimental)
• tools: stonith_admin supports XML output for machine parsing (experimental)
• resources: new HealthIOWait resource agent for node health tracking

Changes since Pacemaker-2.0.1

• Important security fixes for CVE-2018-16878, CVE-2018-16877, CVE-2019-3885
• build: crm_report bug report URL is now configurable at build time
• build: private libpengine/libtransitioner libraries combined as libpacemaker
• controller: avoid memory leak when duplicate monitor is scheduled
• scheduler: respect order constraints when resources are being probed
• scheduler: one group stop shouldn't make another required
• libcrmcommon: handle out-of-range integers in configuration better
• libcrmcommon: export logfile environment variable if using default
• libcrmservice: fix use-after-free memory error in alert handling
• libstonithd: handle more than 64KB output from fence agents

Pacemaker 1.1.21 - Final

Known regressions introduced in this release

• Concurrent fencing actions on a single fence device could be incorrectly blocked (fixed in 1.1.22)

Changes since Pacemaker-1.1.20

• Important security fixes for CVE-2018-16878, CVE-2018-16877, CVE-2019-3885
• tools: ensure crm_resource --cleanup works with multiple failures (regression in 1.1.20)
• build: crm_report bug report URL is now configurable at build time
• crmd: avoid memory leak when duplicate monitor is scheduled
• pengine: respect order constraints when resources are being probed
• pengine: one group stop shouldn't make another required
• pengine: silence log message about symmetrical property of serialize orders
• libcrmcommon: handle out-of-range integers in configuration better
• libcrmservice: fix use-after-free memory error in alert handling

Pacemaker-2.0.2-rc3

This release fixes regressions found in earlier release candidates.

• libstonithd: avoid use-after-free when retrying a failed action
• libcrmcommon: export logfile environment variable if using default
• build: API schemas were unintentionally installed with two packages

Pacemaker-1.1.21-rc1

• Changes since Pacemaker-1.1.20
  • Important security fixes for CVE-2018-16878, CVE-2018-16877, CVE-2019-3885
  • tools: ensure crm_resource --clean-up works with multiple failures (regression in 1.1.20)
  • build: crm_report bug report URL is now configurable at build time
  • crmd: avoid memory leak when duplicate monitor is scheduled
  • pengine: respect order constraints when resources are being probed
  • pengine: one group stop shouldn't make another required
  • pengine: silence log message about symmetrical property of serialize orders
  • libcrmcommon: handle out-of-range integers in configuration better
  • libcrmservice: fix use-after-free memory error in alert handling

Pacemaker-2.0.2-rc2

• Changes since Pacemaker-2.0.2-rc1
  • controller: avoid memory leak when duplicate monitor is scheduled
  • fencing: avoid use-after-free on early failure return
  • libcrmcommon: avoid segfault when beginning formatted text list

Pacemaker-2.0.2-rc1

• Features added since Pacemaker-2.0.1

  • tools: crm_resource --validate can get resource parameters from command line
  • tools: crm_resource --clear prints out any cleared constraints
  • tools: new crm_rule tool for checking rule expiration (experimental)
  • tools: stonith_admin supports XML output for machine parsing (experimental)
  • resources: new HealthIOWait resource agent for node health tracking

• Changes since Pacemaker-2.0.1

  • Important security fixes for CVE-2018-16878, CVE-2018-16877, CVE-2019-3885
  • build: crm_report bug report URL is now configurable at build time
  • build: private libpengine/libtransitioner libraries combined as libpacemaker
  • attrd: prevent race when writer leaves where new writer is not elected
  • controller: prevent race when DC leaves where new DC is not elected
  • scheduler: respect order constraints when resources are being probed
  • scheduler: don't disable waiting for DC fencing
  • scheduler: don't order non-DC shutdowns before DC fencing
  • scheduler: one group stop shouldn't make another required
  • libcrmcommon: handle out-of-range integers in configuration better
  • libcrmservice: cancel in-flight systemd/upstart DBus calls immediately
  • libcrmservice: fix use-after-free memory error in alert handling

Pacemaker 2.0.1 - Final

Known regressions introduced in this release

• Pre-/post-start clone notifications might not be required when they should be (fixed in 2.0.5)

Features added since Pacemaker-2.0.0

• Pacemaker bundles support podman for container management
• fencing: SBD may be used in a cluster that has guest nodes or bundles
• fencing: fencing history is synchronized among all nodes
• fencing: stonith_admin has option to clear fence history
• tools: crm_mon can show fencing action failures and history
• tools: crm_resource --clear supports new --expired option
• Pacemaker Remote: new options to restrict TLS Diffie-Hellman prime length

Changes since Pacemaker-2.0.0

• scheduler: clone notifications could be scheduled for a stopped Pacemaker Remote node and block all further cluster actions (regression since 2.0.0)
• libcrmcommon: correct behavior for completing interrupted live migrations (regression since 2.0.0)
• tools: crm_resource -C could fail to clean up all failures in one run (regression since 2.0.0)
• Pacemaker Remote: avoid unnecessary downtime when moving resource to Pacemaker Remote node that fails to come up (regression since 1.1.18)
• tools: restore stonith_admin ability to confirm unseen nodes are down (regression since 1.1.12)
• build: minor logging fixes to allow compatibility with GCC 9 -Werror
• build: spec file now puts XML schemas in new pacemaker-schemas package
• build: spec file now provides virtual pcmk-cluster-manager package
• pacemaker-attrd: wait a short time before re-attempting failed writes
• pacemaker-attrd: ignore attribute delays when writing after node (re-)join
• pacemaker-attrd: start new election immediately if writer is lost
• pacemaker-attrd: clear election dampening when the writer leaves
• pacemaker-attrd: detect alert configuration changes when CIB is replaced
• CIB: inform originator of CIB upgrade failure
• controller: support resource agents that require node name even for meta-data
• controller: don't record pending clone notifications in CIB
• controller: DC detects completion of another node's shutdown more accurately
• controller: shut down DC if unable to update node attributes
• controller: handle corosync peer/join notifications for new node in any order
• controller: clear election dampening when DC is lost
• executor: cancel recurring monitors if fence device registration is lost
• fencing: check for fence device update when resource defaults change
• fencing: avoid pacemaker-fenced crash possible with stonith_admin misuse
• fencing: limit fencing history to 500 entries
• fencing: stonith_admin now complains if no action option is specified
• pacemakerd: do not modify kernel.sysrq on Linux
• scheduler: regression test compatibility with glib 2.59.0
• scheduler: avoid unnecessary recovery of cleaned guest nodes and bundles
• scheduler: ensure failures causing fencing not expired until fencing done
• scheduler: start unique clone instances in numerical order
• scheduler: convert unique clones to anonymous clones when not supported
• scheduler: associate pending tasks with correct clone instance
• scheduler: ensure bundle clone notifications are directed to correct host
• scheduler: avoid improper bundle monitor rescheduling or fail count clearing
• scheduler: honor asymmetric orderings even when restarting
• scheduler: don't order non-DC shutdowns before DC fencing
• ACLs: assume unprivileged ACL user if can't get user info
• Pacemaker Remote: get Diffie-Hellman prime bit length from GnuTLS API
• libcrmservice: cancel DBus call when cancelling systemd/upstart actions
• libcrmservice: order systemd resources relative to pacemaker_remote
• libpe_status: add public API constructor/destructor for pe_working_set_t
• tools: fix crm_resource --clear when lifetime was used with ban/move
• tools: fix crm_resource --move when lifetime was used with previous move
• tools: make crm_mon CIB connection errors non-fatal if previously successful
• tools: improve crm_mon messages when generating HTML output
• tools: crm_mon cluster connection failure is now "critical" in nagios mode
• tools: crm_mon listing of standby nodes shows if they have active resources
• tools: crm_diff now ignores attribute ordering when comparing in CIB mode
• tools: improve crm_report detection of logs, CIB directory, and processes
• tools: crm_verify returns reliable exit codes
• tools: crm_simulate resource history uses same name as live cluster would

Pacemaker 1.1.20 - Final

Known regressions introduced in this release

• The controller might incorrectly remove a node from DC elections (fixed in 1.1.23)
• crm_resource --cleanup might clean up only some failures (fixed in 1.1.21)

Features added since Pacemaker-1.1.19

• fencing: SBD may now be used in a cluster that has guest nodes or bundles
• fencing: synchronize fencing history among all nodes
• fencing: stonith_admin now has option to clear fence history
• tools: crm_mon now supports showing fencing action failures and history
• tools: crm_resource --clear supports new --expired option
• Pacemaker Remote: option to restrict TLS Diffie-Hellman prime length

Changes since Pacemaker-1.1.19

• Pacemaker Remote: avoid unnecessary downtime when moving resource to
  Pacemaker Remote node that fails to come up (regression since 1.1.18)
• tools: restore stonith_admin ability to confirm unseen nodes are down
  (regression since 1.1.12)
• build: minor logging fixes to allow compatibility with GCC 9 -Werror
• attrd: wait a short time before re-attempting failed writes
• attrd: ignore attribute delays when writing after node (re-)join
• attrd: start new election immediately if writer is lost
• attrd: detect alert configuration changes when CIB is entirely replaced
• attrd: clear election dampening when the writer leaves
• CIB: inform originator of CIB upgrade failure
• crmd: clear election dampening when DC is lost
• fencing: limit fencing history to 500 entries
• fencing: stonith_admin now complains if no action option is specified
• pengine: regression test compatibility with glib 2.59.0
• pengine: don't order non-DC shutdowns before DC fencing
• pengine: avoid unnecessary recovery of cleaned guest nodes
• pengine: convert unique clones to anonymous if not supported by standard
• pengine: don't send clone notifications to a stopped remote node
• pengine: ensure bundle clone notifications are directed to correct host
• pengine: avoid improper bundle monitor rescheduling or fail count clearing
• pengine: honor asymmetric orderings even when restarting
• ACLs: assume unprivileged ACL user if can't get user info
• Pacemaker Remote: get Diffie-Hellman prime bit length from GnuTLS API
• libcrmservice: cancel DBus call when cancelling systemd/upstart actions
• libcrmservice: order systemd resources relative to pacemaker_remote
• libpe_status: add public API constructor/destructor for pe_working_set_t
• tools: fix crm_resource --clear when lifetime was used with ban/move
• tools: fix crm_resource --move when lifetime was used with previous move
• tools: make crm_mon CIB connection errors non-fatal if previously successful
• tools: improve crm_mon messages when generating HTML output
• tools: crm_mon cluster connection failure is now "critical" in nagios mode
• tools: crm_mon listing of standby nodes shows if they have active resources
• tools: improve crm_report detection of logs
• tools: crm_simulate resource history uses same name as live cluster would