Pacemaker 1.1.18 - Release Candidate 2

• Changes since Pacemaker-1.1.18-rc1
  • fix regressions introduced in rc1 (don't break crm_resource --lifetime,
    avoid memory leak when caching meta-data,
    keep previous format of crm_mon XML output for bundles)
  • crm_mon: avoid infinite process spawning if -E script can't be run
  • crm_mon: don't show previous exit-reason for failed action with none
  • libcrmservice: list systemd unit files, not only active units (BZ#5299)
  • libcrmservice: parse long description correctly for LSB meta-data

Pacemaker 1.1.18 - Release Candidate 1

• Features added since Pacemaker-1.1.17

  • warnings are now logged when using legacy syntax to be removed in 2.0
  • agents: ifspeed agent is now installed when building
  • alerts: support alert filters
  • alerts: support alerts for node attribute changes (experimental)
  • crmd,pengine: support unfencing of remote nodes
  • pengine: bundles now support all constraint types
  • pengine: bundles now support rkt containers
  • pengine: bundles support new container-attribute-target parameter
  • pengine: guest nodes are now probed like any other node
  • pengine,tools: logs and crm_mon show why resources changed state
  • stonith-ng: support new fencing resource parameter pcmk_delay_base
  • tools: new crm_resource option --why explains why resources are stopped

• Changes since Pacemaker-1.1.17

  • many documentation improvements
  • agents: ifspeed properly calculates speed of hfi1 interfaces
  • agents: ClusterMon now interprets "update" less than 1000 as seconds
  • attrd: don't lose attributes set between attrd start-up and cluster join
  • attrd: fix multiple minor memory leaks
  • crmd: correctly record that unfencing is complete
  • lrmd: remote resource operations return immediate error if key setup fails
  • pengine: validate no-quorum-policy=suicide correctly
  • pengine: avoid crash when alerts section has comments
  • pengine: detect permanent master scores at start-up
  • pengine: do not re-add a node's default score for each location constraint
  • pengine: allow resources inside bundles to receive clone notifications
  • pengine: default to non-interleaved bundle ordering for safety
  • pengine: ensure bundle nodes and child resources are correctly cleaned up
  • pengine: prevent graph loops when fencing the host underneath a bundle
  • pengine: probe bundle connection resources
  • pengine: bundles now respect PCMK_authkey_location
  • pengine: fix multiple memory issues (use-after-free, use-of-NULL) with bundles
  • pengine: resources in bundles respect failcounts
  • pengine: ensure nested container connections run on the same host
  • pengine: ensure unrecoverable remote nodes are fenced even if no resources can run on them
  • pengine: handle resource migrating behind a migrating remote connection
  • pengine: make sure calculated resource scores are consistent on different architectures
  • pengine: retrigger unfencing for changed device parameters only when necessary
  • stonith-ng: make fencing-device reappear properly after reenabling
  • stonith-ng: include pcmk_on_action in meta-data so 'on' can be overridden
  • tools: allow crm_report to work with no log files specified
  • tools: fix use-after-free in crm_diff introduced in 1.1.17

Pacemaker 1.1.17 - Final

Release info

• Thu Jul 06 2017 Ken Gaillot kgaillot@redhat.com Pacemaker-1.1.17-1
• Changesets: 539
• Diff: 177 files changed, 11525 insertions(+), 5036 deletions(-)

Known regressions introduced in this release

• When run from a Pacemaker Remote node, crm_resource --cleanup incorrectly treats an unspecified node as the local node instead of all nodes (fixed in 2.1.0)
• Pacemaker's systemd unit incorrectly dropped a dependency on DBus (fixed in 2.0.0)
• Mixed-case node names are not handled properly when modifying attributes (fixed in 2.0.0)
• Scheduler can crash when logging ignored failure timeout (fixed in 2.0.0)
• crm_failcount does not handle INFINITY correctly (fixed in 2.0.0)
• crm_diff can have a use-after-free memory error (fixed in 1.1.18)

Features added since Pacemaker-1.1.16

• New "bundle" resource type for Docker container use cases (experimental)
• New "PCMK_node_start_state" environment variable to start node in standby
• New "value-source" rule expression attribute in location constraints to compare a node attribute against a resource parameter
• New "stonith-max-attempts" cluster option to specify how many times fencing can fail for a target before the cluster will no longer immediately re-attempt it (previously hard-coded at 10)
• New "cluster-ipc-limit" cluster option to avoid IPC client eviction in large clusters
• Failures are now tracked per operation type, as well as per node and resource (the "fail-count" and "last-failure" node attribute names now end in "#OPERATION_INTERVAL")
• attrd: Pacemaker Remote node attributes and regular expressions are now supported on legacy cluster stacks (heartbeat, CMAN, and corosync plugin)
• tools: New "crm_resource --validate" option
• tools: New "stonith_admin --list-targets" option
• tools: New "crm_attribute --pattern" option to match a regular expression
• tools: "crm_resource --cleanup" and "crm_failcount" can now take --operation and --interval options to operate on a single operation type

Changes since Pacemaker-1.1.16

• Fix multiple memory issues (leaks, use-after-free) in libraries
• pengine: unmanaging a guest node resource puts guest in maintenance mode
• cib: broadcasts of cib changes should always pass ACL checks
• crmd,libcrmcommon: update throttling when CPUs are hot-plugged
• crmd: abort transition whenever we lose quorum
• crmd: avoid attribute write-out on join when atomic attrd is used
• crmd: check for too many stonith failures only when aborting for that reason
• crmd: correctly clear failure counts only for a specified node
• crmd: don't fence old DC if it's shutting down as soon-to-be DC joins
• crmd: forget stonith failures when forgetting node
• crmd: all nodes should track stonith failure counts in case they become DC
• crmd: update cache status for guest node whose host is fenced
• dbus: prevent lrmd from hanging on dbus calls
• fencing: detect newly added constraints for stonith devices
• pengine: order remote actions after connection recovery (regression introduced in 1.1.15)
• pengine: quicker recovery from failed demote
• libcib: determine remote nodes correctly from node status entries
• libcrmcommon: avoid evicting IPC client if messages spike briefly
• libcrmcommon: better XML comment handling prevents infinite election loop
• libcrmcommon: set month correctly in date/time string sent to alert agents
• libfencing,fencing: intelligently remap "action" wrongly specified in config
• libservices: ensure completed ops aren't on blocked ops list
• libservices: properly detect and cancel in-flight systemd/upstart ops
• libservices: properly watch writable DBus handles
• libservices: systemd service that is reloading doesn't cause monitor failure
• pacemaker_remoted: allow graceful shutdown while unmanaged
• pengine,libpe_status: don't clear same fail-count twice
• pengine: consider guest node unclean if its host is unclean
• pengine: do not re-add a node's default score for each location constraint
• pengine: avoid restarting services when recovering remote connection
• pengine: better guest node recovery when host fails
• pengine: guest node fencing doesn't require stonith enabled
• pengine: allow probes of guest node connection resources
• pengine: properly handle allow-migrate explicitly set for remote connection
• pengine: fence failed remote nodes even if no resources can run on them
• tools: resource agents will now get the correct node name on Pacemaker Remote nodes when using crm_node and crm_attribute
• tools: avoid grep crashes in crm_report when looking for system logs
• tools: crm_resource -C now clears last-failure as well as fail-count
• tools: implement crm_failcount command-line options correctly
• tools: properly ignore version with crm_diff --no-version

Pacemaker 1.1.17 - Release Candidate 4

• Features added since Pacemaker-1.1.17-rc3

  • cib,libcib: support option for IPC eviction threshold

• Changes since Pacemaker-1.1.17-rc3

  • cib: Broadcasts of cib changes should always pass ACLs check
  • libcib: get remoteness correctly from node status
  • libpe_status: avoid memory leaks when creating bundle remote resource
  • libpe_status: disallow resources on bundle nodes
  • pengine: Bundle location constraints should only apply to the IP and docker resources
  • pengine: Clones within bundles may also have notifications enabled
  • pengine: Correctly implement pe_order_implies_first_printed
  • pengine: Do not re-add a node's default score for each location constraint

Pacemaker 1.1.17 - Release Candidate 3

• Features added since Pacemaker-1.1.17-rc2

  • Support inheritable meta-attributes for bundles

• Changes since Pacemaker-1.1.17-rc2

  • crmd: avoid attribute write-out on join when atomic attrd is used

Pacemaker-1.1.17-rc2

• Update source tarball to revision: 8fdb646

• Changesets: 19

• Diff: 10 files changed, 99 insertions(+), 58 deletions(-)

• Changes since Pacemaker-1.1.17-rc1

  • fencing: Detect newly added constraints for stonith devices
  • pengine,libpe_status: multiple bug fixes for new bundle feature
  • pengine: Order remote actions after connection recovery
    (regression introduced in 1.1.15)

Pacemaker 1.1.17 - Release Candidate 1

• Update source tarball to revision: 61538e9

• Changesets: 440

• Diff: 163 files changed, 10085 insertions(+), 4416 deletions(-)

• Features added since Pacemaker-1.1.16

  • New "bundle" resource type for Docker container use cases (experimental)
  • New "PCMK_node_start_state" environment variable to start node in standby
  • New "value-source" rule expression attribute in location constraints to compare a node attribute against a resource parameter
  • New "stonith-max-attempts" cluster option to specify how many times fencing can fail for a target before the cluster will no longer immediately re-attempt it (previously hard-coded at 10)
  • Failures are now tracked per operation type, as well as per node and resource (the "fail-count" and "last-failure" node attribute names now end in "#OPERATION_INTERVAL")
  • attrd: Pacemaker Remote node attributes and regular expressions are now supported on legacy cluster stacks (heartbeat, CMAN, and corosync plugin)
  • tools: New "crm_resource --validate" option
  • tools: New "stonith_admin --list-targets" option
  • tools: New "crm_attribute --pattern" option to match a regular expression
  • tools: "crm_resource --cleanup" and "crm_failcount" can now take --operation and --interval options to operate on a single operation type

• Changes since Pacemaker-1.1.16

  • Fix multiple memory issues (leaks, use-after-free) in libraries
  • pengine: unmanaging a guest node resource puts guest in maintenance mode
  • crmd,libcrmcommon: update throttling when CPUs are hot-plugged
  • crmd: check for too many stonith failures only when aborting for that reason
  • crmd: correctly clear failure counts only for a specified node
  • crmd: don't fence old DC if it's shutting down as soon-to-be DC joins
  • crmd: forget stonith failures when forgetting node
  • crmd: all nodes should track stonith failure counts in case they become DC
  • crmd: update cache status for guest node whose host is fenced
  • dbus: prevent lrmd from hanging on dbus calls
  • pengine: quicker recovery from failed demote
  • libcrmcommon: avoid evicting IPC client if messages spike briefly
  • libcrmcommon: better XML comment handling prevents infinite election loop
  • libfencing,fencing: intelligently remap "action" wrongly specified in config
  • libservices: ensure completed ops aren't on blocked ops list
  • libservices: properly detect and cancel in-flight systemd/upstart ops
  • libservices: properly watch writable DBus handles
  • libservices: systemd service that is reloading doesn't cause monitor failure
  • pacemaker_remoted: allow graceful shutdown while unmanaged
  • pengine,libpe_status: don't clear same fail-count twice
  • pengine: consider guest node unclean if its host is unclean
  • pengine: better guest node recovery when host fails
  • pengine: guest node fencing doesn't require stonith enabled
  • pengine: allow probes of guest node connection resources
  • pengine: properly handle allow-migrate explicitly set for remote connection
  • tools: resource agents will now get the correct node name on Pacemaker Remote nodes when using crm_node and crm_attribute
  • tools: avoid grep crashes in crm_report when looking for system logs
  • tools: crm_resource -C now clears last-failure as well as fail-count
  • tools: implement crm_failcount command-line options correctly
  • tools: properly ignore version with crm_diff --no-version

Pacemaker 1.1.16 - Final

Known regressions introduced in this release

• None

Features added since Pacemaker-1.1.15

• Location constraints may use rsc-pattern, with submatches expanded
• node-health-base available with node-health-strategy=progressive
• new Pacemaker Development document for working on pacemaker code base
• new PCMK_panic_action variable allows crash instead of reboot on panic
• resources: add resource agent for managing a node attribute
• systemd: include socket units when listing all systemd agents

Changes since Pacemaker-1.1.15

• Important security fix for CVE-2016-7035
• Logging is now synchronous when blackboxes are enabled
• All python code except CTS is now compatible with python 2.6+ and 3.2+
• build: take advantage of compiler features for security and performance
• build: update SuSE spec modifications for recent spec changes
• build: avoid watchdog reboot when upgrading pacemaker_remote with sbd
• build: numerous other improvements in environment detection, etc.
• cib: fix infinite loop when no schema validates
• crmd: cl#5185 - record pending operations in CIB before they are performed
• crmd: don't abort transitions for CIB comment changes
• crmd: resend shutdown request if DC loses original request
• documentation: install improved README in doc instead of now-removed AUTHORS
• documentation: clarify licensing and provide copy of all licenses
• documentation: document various features and upgrades better
• fence_legacy: use "list" action when searching cluster-glue agents
• libcib: don't stop sending alerts after releasing DC role
• libcrmcommon: properly handle XML comments when comparing v2 patchset diffs
• libcrmcommon: report errors consistently when waiting for data on connection
• libpengine: avoid potential use-of-NULL
• libservices: use DBusError API properly
• pacemaker_remote: init script stop should always return 0
• pacemaker_remote: allow remote clients to timeout/reconnect
• pacemaker_remote: correctly calculate remaining timeout when receiving messages
• pengine: avoid transition loop for start-then-stop + unfencing
• pengine: correctly update dependent actions of un-runnable clones
• pengine: do not fence a node in maintenance mode if it shuts down cleanly
• pengine: set OCF_RESKEY_CRM_meta_notify_active_* for multistate resources
• resources: ping - avoid temporary files for fping check, support FreeBSD
• resources: SysInfo - better support for FreeBSD
• resources: variable name typo in docker-wrapper
• systemd: order pacemaker after time-sync target
• tools: correct attrd_updater help and error messages when using CMAN
• tools: crm_standby --version/--help should work without cluster running
• tools: make crm_report sanitize CIB before generating readable version
• tools: display pending resource state by default when available
• tools: avoid matching other process with same PID in ClusterMon

Pacemaker 1.1.16 - Release Candidate 2

Changes since Pacemaker-1.1.16-rc1

• Fix minor build issue
• Correct license specified for some library source files to LGPL
• systemd: order pacemaker after time-sync target

Pacemaker 1.1.16 - Release Candidate 1

• Thu Nov 03 2016 Ken Gaillot kgaillot@redhat.com Pacemaker-1.1.16-rc1
• Update source tarball to revision: 2fc4716
• Changesets: 360
• Diff: 148 files changed, 7187 insertions(+), 5592 deletions(-)
• Features added since Pacemaker-1.1.15
  • Location constraints may use rsc-pattern, with submatches expanded
  • node-health-base available with node-health-strategy=progressive
  • new Pacemaker Development document for working on pacemaker code base
  • new PCMK_panic_action variable allows crash instead of reboot on panic
  • resources: add resource agent for managing a node attribute
  • systemd: include socket units when listing all systemd agents
• Changes since Pacemaker-1.1.15
  • Important security fix for CVE-2016-7035
  • Logging is now synchronous when blackboxes are enabled
  • All python code except CTS is now compatible with python 2.6+ and 3.2+
  • build: take advantage of compiler features for security and performance
  • build: update SuSE spec modifications for recent spec changes
  • build: avoid watchdog reboot when upgrading pacemaker_remote with sbd
  • build: numerous other improvements in environment detection, etc.
  • cib: fix infinite loop when no schema validates
  • crmd: cl#5185 - record pending operations in CIB before they are performed
  • crmd: don't abort transitions for CIB comment changes
  • crmd: resend shutdown request if DC loses original request
  • documentation: install improved README in doc instead of now-removed AUTHORS
  • documentation: clarify licensing and provide copy of all licenses
  • documentation: document various features and upgrades better
  • fence_legacy: use "list" action when searching cluster-glue agents
  • libcib: don't stop sending alerts after releasing DC role
  • libcrmcommon: properly handle XML comments when comparing v2 patchset diffs
  • libcrmcommon: report errors consistently when waiting for data on connection
  • libpengine: avoid potential use-of-NULL
  • libservices: use DBusError API properly
  • pacemaker_remote: init script stop should always return 0
  • pacemaker_remote: allow remote clients to timeout/reconnect
  • pacemaker_remote: correctly calculate remaining timeout when receiving messages
  • pengine: avoid transition loop for start-then-stop + unfencing
  • pengine: correctly update dependent actions of un-runnable clones
  • pengine: do not fence a node in maintenance mode if it shuts down cleanly
  • pengine: set OCF_RESKEY_CRM_meta_notify_active_* for multistate resources
  • resources: ping - avoid temporary files for fping check, support FreeBSD
  • resources: SysInfo - better support for FreeBSD
  • resources: variable name typo in docker-wrapper
  • tools: correct attrd_updater help and error messages when using CMAN
  • tools: crm_standby --version/--help should work without cluster running
  • tools: make crm_report sanitize CIB before generating readable version
  • tools: display pending resource state by default when available
  • tools: avoid matching other process with same PID in ClusterMon