Skip to content

Releases: ClusterLabs/pacemaker

Pacemaker-1.1.21-rc1

24 May 15:32
Compare
Choose a tag to compare
Pacemaker-1.1.21-rc1 Pre-release
Pre-release
  • 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

21 May 16:30
Compare
Choose a tag to compare
Pacemaker-2.0.2-rc2 Pre-release
Pre-release
  • 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

25 Apr 01:22
a365fc5
Compare
Choose a tag to compare
Pacemaker-2.0.2-rc1 Pre-release
Pre-release
  • 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

04 Mar 19:57
9e909a5
Compare
Choose a tag to compare

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

04 Mar 19:59
3c4c782
Compare
Choose a tag to compare

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

Pacemaker 1.1.20 - Release Candidate 3

26 Feb 23:18
4601a8f
Compare
Choose a tag to compare
Pre-release
  • Changes since Pacemaker-1.1.20-rc2
    • scheduler: regression test compatibility with glib 2.59.0

Pacemaker 2.0.1 - Release Candidate 5

25 Feb 21:37
22ee9a7
Compare
Choose a tag to compare
Pre-release
  • Changes since Pacemaker-2.0.1-rc4
    • scheduler: regression test compatibility with glib 2.59.0

Pacemaker 1.1.20 - Release Candidate 2

31 Jan 21:51
Compare
Choose a tag to compare
Pre-release
  • Changes since Pacemaker-1.1.20-rc1
    • attrd: clear election dampening when the writer leaves
    • crmd: clear election dampening when DC is lost
    • pengine: don't order non-DC shutdowns before DC fencing
    • libcrmservice: cancel DBus call when cancelling systemd/upstart actions
    • tools: remove duplicate fence history state in crm_mon XML output
    • build: minor logging fixes to allow compatibility with GCC 9 -Werror

Pacemaker 2.0.1 - Release Candidate 4

30 Jan 17:02
57cc9c1
Compare
Choose a tag to compare
Pre-release
  • Changes since Pacemaker-2.0.1-rc3
    • attrd: clear election dampening when the writer leaves
    • controller: clear election dampening when DC is lost
    • scheduler: don't order non-DC shutdowns before DC fencing
    • libcrmservice: cancel DBus call when cancelling systemd/upstart actions
    • tools: remove duplicate fence history state in crm_mon XML output
    • build: offer configure option to disable tests broken with glib 2.59.0
    • build: minor logging fixes to allow compatibility with GCC 9 -Werror

Pacemaker 1.1.20 - Release Candidate 1

14 Jan 22:46
Compare
Choose a tag to compare
Pre-release
  • 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

    • tools: restore stonith_admin ability to confirm unseen nodes are down
      (regression since 1.1.12)
    • Pacemaker Remote: avoid unnecessary downtime when moving resource to
      Pacemaker Remote node that fails to come up (regression since 1.1.18)
    • 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
    • CIB: inform originator of CIB upgrade failure
    • fencing: limit fencing history to 500 entries
    • fencing: stonith_admin now complains if no action option is specified
    • pengine: avoid unnecessary recovery of cleaned guest nodes
    • pengine: convert unique clones to anonymous clones 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 monitor rescheduling or fail count clearing for bundles
    • 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: order systemd resources relative to pacemaker_remote
    • libpe_status: add public API constructor/destructor for pe_working_set_t
    • tools: fix crm_resource --clear/--move when lifetime was used with previous ban/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 now shows if they still have active resources
    • tools: improve crm_report detection of logs
    • tools: crm_simulate simulated resource history uses same name as live cluster would