Pacemaker 1.1.22 - Final

Known regressions introduced in this release

• None

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: avoid invalid transition when guest node host is not fenceable
• 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 - Final

Known regressions introduced in this release

• The -T/--tag option to stonith_admin stopped working (fixed in 2.1.3)
• crm_mon can crash when running in daemon mode with CGI output (fixed in 2.1.0)
• HTTP headers could be incorrectly added when crm_mon is run in daemon mode (fixed in 2.0.5)
• Expected score of ping attributes are incorrectly omitted from crm_mon XML output (fixed in 2.0.5)

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: more cluster properties support ISO 8601 time specifications
• 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 CSS stylesheet
• tools: stonith_admin supports HTML output in addition to text and XML
• tools: crm_simulate supports --repeat option to repeat profiling tests
• tools: new pcmk_simtimes tool compares crm_simulate profiling output
• agents: SysInfo supports K, T, and P units in addition to Kb and G

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 "T "
• rpm: pacemaker-cts package now explicitly requires pacemaker-cli
• 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: wait for probe actions to complete to prevent unnecessary restart/re-promote of dependent resources
• scheduler: avoid invalid transition when guest node host is not fenceable
• scheduler: properly detect dangling migrations, to avoid restart loop
• scheduler: avoid scheduling actions on remote node that is shutting down
• scheduler: avoid delay in recovery of failed remote connections
• scheduler: clarify action failure log messages by including failure time
• scheduler: calculate secure digests for unfencing, for replaying saved CIBs
• 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: count disabled/blocked resources correctly in crm_mon/crm_simulate
• tools: crm_mon --interval now accepts ISO 8601 and has correct help
• tools: organize crm_mon text output with list headings, indents, bullets
• tools: crm_report: fail if tar is not available
• tools: crm_report: correct 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

Pacemaker 2.0.3 - Release Candidate 3

• Changes since Pacemaker-2.0.3-rc2
  • logging: Clarify action failure messages by including failure time
  • tools: Fix several minor crm_mon regressions introduced in 2.0.3-rc1
  • tools: Rename new crm_mon options introduced in 2.0.3-rc1 for clarity
  • tools: Count disabled/blocked resources correctly in crm_mon/crm_simulate

Pacemaker 2.0.3 - Release Candidate 2

• Changes since Pacemaker-2.0.3-rc1
  • rpm: pacemaker-cts package now explicitly requires pacemaker-cli
  • scheduler: avoid invalid transition when guest node host is not fenceable
  • tools: minor rc1 regression fixes in crm_mon
  • tools: crm_mon --interval now accepts ISO 8601 and has detailed help

Pacemaker 1.1.22 - Release Candidate 2

• Changes since Pacemaker-1.1.22-rc1
  • pengine: avoid invalid transition when guest node host is not fenceable

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