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 [email protected] 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

Pacemaker 1.1.15 - Final

Known regressions introduced in this release

• CLBZ#5309: a reload and a restart of the same resource can be scheduled in the same transition (fixed in 1.1.18)
• Remote actions can be scheduled before connection recovery if both are needed in same transition (fixed in 1.1.17)

Features added since Pacemaker-1.1.14

• Event-driven alerts allow scripts to be called after significant events
• build: Some files moved from pacemaker package to pacemaker-cli for cleaner pacemaker-remote dependencies
• build: ./configure --with-configdir argument for /etc/sysconfig, /etc/default, etc.
• fencing: Simplify watchdog integration
• fencing: Support concurrent fencing actions via new pcmk_action_limit option
• remote: pacemaker_remote may be stopped without disabling resource first
• remote: Report integration status of Pacemaker Remote nodes in CIB node_state
• tools: crm_mon now reports why resources are not starting
• tools: crm_report now obscures passwords in logfiles
• tools: attrd_updater --update-both/--update-delay options allow changing dampening value
• tools: allow stonith_admin -H '*' to show history for all nodes

Changes since Pacemaker-1.1.14

• Fix multiple memory issues (leaks, use-after-free) in daemons, libraries and tools
• Make various log messages more user-friendly
• Improve FreeBSD and Hurd support
• attrd: Prevent possible segfault on exit
• cib: Fix regression to restore support for compressed CIB larger than 1MB
• common: fix regression in 1.1.14 that made have-watchdog always true
• controld: handle DLM "wait fencing" state better
• crmd: Fix regression so that fenced unseen nodes do not remain unclean
• crmd: Take start-delay into account when calculation action timeouts
• crmd: Avoid timeout on older peers when cancelling a resource operation
• fencing: Allow fencing by node ID (e.g. by DLM) even if node left cluster
• lrmd: Fix potential issues when cluster is stopped via systemd shutdown
• pacemakerd: Properly respawn stonithd if it fails
• pengine: Fix regression with multiple monitor levels that could ignore failure
• pengine: Correctly set OCF_RESKEY_CRM_meta_timeout when start-delay is configured
• pengine: Properly order actions for master/slave resources in anti-colocations
• pengine: Respect asymmetrical ordering when trying to move resources
• pengine: Properly order stop actions on guest node relative to host stonith
• pengine: Correctly block actions dependent on unrunnable clones
• remote: Allow remote nodes to have node attributes even with legacy attrd
• remote: Recover from remote node fencing more quickly
• remote: Place resources on newly rejoined remote nodes more quickly
• resources: ping agent can now use fping6 for IPv6 hosts
• resources: SysInfo now resets #health_disk to green when there's sufficient free disk
• tools: crm_report is now more efficient and handles Pacemaker Remote nodes better
• tools: Prevent crm_resource segfault when --resource is not supplied with --restart
• tools: crm_shadow --display option now works
• tools: crm_resource --restart handles groups, target-roles and moving resources better

Pacemaker 1.1.15 - Release Candidate 4

• Features added since Pacemaker-1.1.15-rc3
  • sample alert scripts are now installed in /usr/share/pacemaker/alerts
  • stonith_admin: allow -H '*' to show history for all nodes
  • ./configure --with-configdir argument for /etc/sysconfig, /etc/default, etc.
• Changes since Pacemaker-1.1.15-rc3
  • fix multiple memory issues (leaks, use-after-free) in daemons and libraries
  • improve FreeBSD support
  • Bug rhbz#1321711: handle DLM "wait fencing" state better in controld agent
  • crmd: avoid timeout on older peers when cancelling a resource operation
  • pengine: properly order stop actions on guest node relative to host stonith
  • tools: don't require node to be known to crm_resource when deleting attribute
  • tools: consistently print ms resource state in crm_mon
  • tools: update crm_mon schema for recent changes

Pacemaker 1.1.15 - Release Candidate 3

Changes since Pacemaker-1.1.15-rc2

• make various log messages more user-friendly
• improve FreeBSD and Hurd support
• Bug cl#5266: log correct directory name that daemons change to
• Bug cl#5270: make systemd overrides world-readable to avoid log warnings
• Bug cl#5272: validate attrd requests better
• Bug rhbz#1321711: handle DLM "wait fencing" state better in controld agent
• Bug rhbz#1338623: fix 1.1.15-rc1 regression in attrd when node ID is reused
• libcrmcommon: fix regression in 1.1.14 that made have-watchdog always true

Pacemaker 1.1.15 - Release Candidate 2

• Changes since Pacemaker-1.1.15-rc1
  • attrd: Fix issue introduced in 1.1.15-rc1 breaking the synchronization of attributes
  • attrd: If attribute delay changes, update it when synchronizing attributes
  • crmd: Rename alerts' tstamp_format to timestamp-format and default to "%H:%M:%S.%06N"
  • crmd: Take start-delay into account for the timeout of the action timer
  • pengine: Correctly set OCF_RESKEY_CRM_meta_timeout when start-delay is configured
  • pengine: Properly order actions for master/slave resources in anti-colocations
  • pengine: Respect asymmetrical ordering when trying to move resources
  • resources: SysInfo now resets #health_disk to green when there's sufficient free disk

Pacemaker 1.1.15 - Release Candidate 1

• Features added since Pacemaker-1.1.14
  • Event-driven alerts allow scripts to be called after significant events
  • Move some files from pacemaker package to pacemaker-cli for cleaner pacemaker-remote dependencies
  • fencing: Simplify watchdog integration
  • fencing: Support concurrent fencing actions via new pcmk_action_limit option
  • remote: pacemaker_remote may be stopped without disabling resource first
  • remote: Report integration status of Pacemaker Remote nodes in CIB node_state
  • tools: crm_mon now reports why resources are not starting
  • tools: crm_report now obscures passwords in logfiles
  • tools: attrd_updater --update-both/--update-delay options allow changing dampening value
• Changes since Pacemaker-1.1.14
  • Fix multiple memory issues (leaks, use-after-free) in daemons and libraries
  • cib: Fix regression to restore support for compressed CIB larger than 1MB
  • crmd: Fix regression so that fenced unseen nodes do not remain unclean
  • fencing: Allow fencing by node ID (e.g. by DLM) even if node left cluster
  • lrmd: Fix potential issues when cluster is stopped via systemd shutdown
  • pacemakerd: Properly respawn stonithd if it fails
  • pengine: Fix regression with multiple monitor levels that could ignore failure
  • remote: Allow remote nodes to have node attributes even with legacy attrd
  • remote: Recover from remote node fencing more quickly
  • remote: Place resources on newly rejoined remote nodes more quickly
  • resources: ping agent can now use fping6 for IPv6 hosts
  • tools: crm_report is now more efficient and handles Pacemaker Remote nodes better
  • tools: Prevent crm_resource segfault when --resource is not supplied with --restart
  • tools: crm_shadow --display option now works

Pacemaker 1.1.14 - Final

Release info

• Thu Jan 14 2016 Ken Gaillot [email protected] Pacemaker-1.1.14-1
• Changesets: 724
• Diff: 179 files changed, 13142 insertions(+), 7695 deletions(-)

Known regressions introduced in this release

• The have-watchdog cluster property is always true (fixed in 1.1.15)
• When run from a Pacemaker Remote node, attrd_updater --query treats an unspecified node as the local node instead of all nodes (fixed in 2.1.0)

Features added since Pacemaker-1.1.13

• crm_resource: Indicate common reasons why a resource may not start after a cleanup
• crm_resource: New --force-promote and --force-demote options for debugging
• fencing: Support targeting fencing topologies by node name pattern or node attribute
• fencing: Remap sequential topology reboots to all-off-then-all-on
• pengine: Allow resources to start and stop as soon as their state is known on all nodes
• pengine: Include a list of all and available nodes with clone notifications
• pengine: Addition of the clone resource clone-min metadata option
• pengine: Support of multiple-active=block for resource groups
• remote: Resources that create guest nodes can be included in a group resource
• remote: reconnect_interval option for remote nodes to delay reconnect after fence

Changes since Pacemaker-1.1.13

• improve support for building on FreeBSD and Debian
• fix multiple memory issues (leaks, use-after-free, double free, use-of-NULL) in components and tools
• cib: Do not terminate due to badly behaving clients
• cman: handle corosync-invented node names of the form Node{id} for peers not in its node list
• controld: replace bashism
• crm_node: Display node state with -l and quorum status with -q, if available
• crmd: resources would sometimes be restarted when only non-unique parameters changed
• crmd: fence remote node after connection failure only once
• crmd: handle resources named the same as cluster nodes
• crmd: Pre-emptively fail in-flight actions when lrmd connections fail
• crmd: Record actions in the CIB as failed if we cannot execute them
• crm_report: Enable password sanitizing by default
• crm_report: Allow log file discovery to be disabled
• crm_resource: Allow the resource configuration to be modified for --force-{check,start,..} calls
• crm_resource: Compensate for -C and -p being called with the child resource for clones
• crm_resource: Correctly clean up all children for anonymous cloned groups
• crm_resource: Correctly clean up failcounts for inactive anonymous clones
• crm_resource: Correctly observe --force when deleting and updating attributes
• crm_shadow: Fix "crm_shadow --diff"
• crm_simulate: Prevent segfault on arches with 64bit time_t
• fencing: ensure "required"/"automatic" only apply to "on" actions
• fencing: Return a provider for the internal fencing agent "#watchdog" instead of logging an error
• fencing: ignore stderr output of fence agents (often used for debug messages)
• fencing: fix issue where deleting a fence device attribute can delete the device
• libcib: potential user input overflow
• libcluster: overhaul peer cache management
• log: make syslog less noisy
• log: fix various misspellings in log messages
• lrmd: cancel currently pending STONITH op if stonithd connection is lost
• lrmd: Finalize all pending and recurring operations when cleaning up a resource
• pengine: Bug cl#5247 - Imply resources running on a container are stopped when the container is stopped
• pengine: cl#5235 - Prevent graph loops that can be introduced by "load_stopped -> migrate_to" ordering
• pengine: Correctly bypass fencing for resources that do not require it
• pengine: do not timeout remote node recurring monitor op failure until after fencing
• pengine: Ensure recurring monitor operations are cancelled when clone instances are de-allocated
• pengine: fixes segfault in pengine when fencing remote node
• pengine: properly handle blocked clone actions
• pengine: ensure failed actions that occurred in node shutdown are displayed
• remote: Correctly display the usage of the ocf:pacemaker:remote resource agent
• remote: do not fail operations because of a migration
• remote: enable reloads for select remote connection options
• resources: allow for top output with or without percent sign in HealthCPU
• resources: Prevent an error message on stopping "Dummy" resource
• systemd: Prevent segfault when logging failed operations
• systemd: Reconnect to System DBus if the connection is closed
• systemd: set systemd resources' timeout values higher than systemd's own default
• tools: Do not send command lines to syslog
• tools: update SNMP MIB
• upstart: Ensure pending structs are correctly unreferenced