Pacemaker 2.0.4 Final

Regressions introduced in this release

• crm_error prints spurious output when given a negative return code argument (fixed in 2.1.5)
• crm_mon --hide-headers and related options stopped working (fixed in 2.1.2)
• The executor can crash after TLS errors (fixed in 2.1.1)
• crm_mon can leak memory when filtering by resource (fixed in 2.1.1)
• The --version argument to crm_rule, crm_error, crm_diff, and crm_node incorrectly exits with status 64 instead of 0 (fixed in 2.1.1)
• The --version argument to crm_simulate incorrectly exits with status 64 instead of 0 (fixed in 2.1.0)
• crm_mon incorrectly omits the node name for bundle instances (fixed in 2.0.5)
• The stonith_admin --list-targets option stopped working (fixed in 2.0.5)

Features added since Pacemaker-2.0.3

• build: Add support for glib-based unit tests.
• controller: add new feature 'shutdown-locks' to optionally allow a gracefully shutdown node to have the resources locked to it for a configurable time, so that it can be restarted with exactly the same resources running as before
• controller/fencing/scheduler: add new feature 'priority-fencing-delay' to optionally derive the priority of a node from the resource-priorities of the resources it is running. In a fencing-race the node with the highest priority has a certain advantage over the others as fencing requests for that node are executed with an additional delay. controlled via cluster option priority-fencing-delay (default = 0)
• stonith_admin: add --delay option (default = 0) to support enforced fencing delay
• tools: Add --include= and --exclude= to crm_mon
• tools: Add --node= to filter crm_mon output for a node (or tag)
• tools: Allow more fine grained filtering of fence-history in crm_mon
• tools: Allow crm_rule to check some date_specs

Fixes for regressions introduced in Pacemaker-2.0.0

• tools: ensure that getting the local node name using crm_node always works from Pacemaker Remote node command line

Changes since Pacemaker-2.0.3

• build: improve checking headers for C++ fitness
• build: restore build on latest OpenSUSE
• fencing: Report an error getting history in output instead of empty history
• fencing: Improve parameter handling for RHCS-style fence-agents
  - make parameter action shown as not required
  - add port or plug parameter according to metadata
  - plug parameter shown as non-required in the metadata
• controller: clear leaving node's transient attributes even if there is no DC
• controller: don't ack same request twice
• iso8601: Fix crm_time_parse_offset() to parse offset with plus sign.
• libcrmcommon, libpe: validate interval specs correctly
• libcrmcommon: Add pcmk_str_is_infinity, pcmk_str_is_minus_infinity and pcmk__unregister_formats.
• libcrmcommon: Extend what pcmk__split_range can do
• libfencing: Export formatted output functions
• libpe_status: Add node list arg to output messages preventing weird behavior + potential segfaults
• libpe_status: Update the maint mode message for HTML output
• fencing, tools: Fix arguments to stonith-event
• scheduler: don't incorporate dependencies' colocations multiple times
• scheduler: ensure attenuated scores still have some effect
• scheduler: ignore colocation constraints with 0 score
• scheduler: make sure cluster-wide maintenance-mode=true overrides per-resource settings
• scheduler: properly detect whether guest node is fenceable
• scheduler: do not differentiate case where all the nodes have equal priority
• tests: Add tests for pe_cron_range_satisfied
• tests: Add tests for the current behavior of pcmk__split_range
• tools, lib: Use standard pacemaker return codes in crm_rule
• tools: Correct stonith-event arguments in crm_mon
• tools: Fix man pages for crm_mon & crm_diff
• tools: Make crm_mon --interval understand more formats
• tools: Fix --html-title= in crm_mon.
• tools: Print errors to stderr for crm_mon's legacy xml.
• tools: use return codes consistently in stonith_admin
• tools: Use glib for cmdline handling in crm_diff, crm_simulate & crm_error
• xml: Add a new version of the tags schema.
• based: populate cib_nodes when 'cibadmin -R -scope=configuration'
• cibsecret: don't use pssh -q option unless supported
• fencing: avoid infinite loop if device is removed during operation
• fencing: avoid possible use-of-NULL when parsing metadata
• fencing: Remove dangling 'pending' for completed DC fencing. (CLBZ#5401)

Pacemaker 2.0.4 - Release Candidate 3

• Fixes for regressions / new buggy features introduced in Pacemaker-2.0.4-rc1

  • libpe_status: Modify filtering of inactive resources.

• Changes since Pacemaker-2.0.4-rc2

  • based: use crm_exit to free qb-logging on daemon exit.
  • cts: handle last-run= and last-rc-change= as full date strings.

Pacemaker 1.1.23 - Release Candidate 1

• Features added since Pacemaker-1.1.22

  • fencing: improve parameter handling for RHCS-style fence agents
    - add port or plug parameter according to metadata
    - plug parameter shown as non-required in the metadata
  • tools: add stonith_admin --delay option (default = 0) to support enforced fencing delay

• Changes since Pacemaker-1.1.22

  • crmd: properly detect node info requests from remote nodes (regression introduced in 1.1.19)
  • crmd: remove node as voter only if lost (regression introduced in 1.1.20)
  • crmd: clear leaving node's transient attributes even if there is no DC
  • crmd: don't ack same request twice
  • crmd: avoid delay when recovering resources after shutdown-lock expiration (BZ#5424)
  • fencing: remove dangling 'pending' for completed DC fencing (BZ#5401)
  • fencing: avoid possible use-of-NULL when parsing metadata
  • fencing: "action" now shown as not required in agent metadata
  • libcrmcommon: fix parsing ISO 8601 offsets with a plus sign
  • libcrmcluster: use proper type for corosync id when updating node state
  • pengine: don't incorporate dependencies' colocations multiple times
  • pengine: ensure attenuated scores still have some effect
  • pengine: ignore colocation constraints with 0 score
  • pengine: make sure cluster-wide maintenance-mode=true overrides per-resource settings

The priority-fencing-delay feature from the Pacemaker 2.0.4 release can be enabled for this release by building with -DENABLE_PRIORITY_FENCING_DELAY in CFLAGS, but be aware that unexpected behavior may result in mixed-version clusters or after an upgrade to a 2.0 version earlier than 2.0.4.

Pacemaker 2.0.4 - Release Candidate 2

• Fixes for regressions introduced in Pacemaker-2.0.0

  • controller: properly detect remote node info requests

• Fixes for regressions / new buggy features introduced in Pacemaker-2.0.4-rc1

  • libpe_status: Apply node filtering to clone resource lists.
  • libpe_status: Don't filter in pe__bundle_replica_output_text.
  • libpe_status: Don't output unnecessary resource headers.
  • libpe_status: Handle filtering of inactive resources.
  • tools: get stonith_admin --list-targets working again
  • tools: Print inactive resources by default with crm_mon xml output.

• Changes since Pacemaker-2.0.4-rc1

  • fencer: avoid infinite loop if device is removed during operation
  • fencer: avoid possible use-of-NULL when parsing metadata
  • libfencing, fencer: Improve parameter handling for RHCS-style fence-agents
    - add port or plug parameter according to metadata
    - plug parameter shown as non-required in the metadata
  • controld: Avoid delay when recovering resources after shutdown-lock
    expiration. (CLBZ#5424)
  • fencing: Remove dangling 'pending' for completed DC fencing. (CLBZ#5401)

Pacemaker 2.0.4 - Release Candidate 1

• Features added since Pacemaker-2.0.3

  • build: Add support for glib-based unit tests.
  • controller: add new feature 'shutdown-locks'
    Optionally allow a gracefully shutdown node to have the resources
    locked to it for a configurable time.
    So that it can be restarted with exactly the same resources
    running as before.
  • controller/fencer/scheduler: add new feature 'priority-fencing-delay'
    Optionally derive the priority of a node from the resource-priorities
    of the resources it is running.
    In a fencing-race the node with the highest priority has a certain
    advantage over the others as fencing requests for that node are
    executed with an additional delay.
    controlled via cluster option priority-fencing-delay (default = 0)
  • stonith_admin: add --delay option (default = 0) to support enforced
    fencing delay
  • tools: Add --include= and --exclude= to crm_mon.
  • tools: Add --node= to filter crm_mon output for a node (or tag).
  • tools: Allow more fine grained filtering of fence-history in crm_mon.
  • tools: Allow crm_rule to check some date_specs.

• Changes since Pacemaker-2.0.3

  • build: improve checking headers for C++ fitness
  • build: restore build on latest OpenSUSE
  • libstonithd: Report an error getting history in output instead of
    empty history
  • libstonithd: Improve parameter handling for RHCS-style fence-agents
    - make parameter action shown as not required
  • controller: clear leaving node's transient attributes even if there is no DC
  • controller: don't ack same request twice
  • iso8601: Fix crm_time_parse_offset() to parse offset with plus sign.
  • libcrmcommon, libpe: validate interval specs correctly
  • libcrmcommon: Add pcmk_str_is_infinity, pcmk_str_is_minus_infinity and
    pcmk__unregister_formats.
  • libcrmcommon: Extend what pcmk__split_range can do.
  • libfencing: Export formatted output functions.
  • libpe_status: Add node list arg to output messages preventing weird
    behavior + potential segfaults
  • libpe_status: Update the maint mode message for HTML output.
  • libstonithd, tools: Fix arguments to stonith-event.
  • scheduler: don't incorporate dependencies' colocations multiple times
  • scheduler: ensure attenuated scores still have some effect
  • scheduler: ignore colocation constraints with 0 score
  • scheduler: make sure cluster-wide maintenance-mode=true overrides
    per-resource settings
  • scheduler: properly detect whether guest node is fenceable
  • scheduler: do not differentiate case where all the nodes have equal priority
  • tests: Add tests for pe_cron_range_satisfied.
  • tests: Add tests for the current behavior of pcmk__split_range.
  • tools, lib: Use standard pacemaker return codes in crm_rule.
  • tools: Correct stonith-event arguments in crm_mon.
  • tools: Fix man pages for crm_mon & crm_diff.
  • tools: Make crm_mon --interval understand more formats.
  • tools: Fix --html-title= in crm_mon.
  • tools: Print errors to stderr for crm_mon's legacy xml.
  • tools: use return codes consistently in stonith_admin
  • tools: Use glib for cmdline handling in crm_diff, crm_simulate & crm_error
  • xml: Add a new version of the tags schema.
  • based: populate cib_nodes when 'cibadmin -R -scope=configuration'

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