Skip to content

Releases: ClusterLabs/pacemaker

Pacemaker 2.1.1 - Final

09 Sep 23:07
Compare
Choose a tag to compare

Known regressions introduced in this release

  • The executor may have a double-free error when performing notifications (fixed in 2.1.3)
  • pacemakerd -S no longer waits for cluster to shut down before returning (fixed in 2.1.6)

Features added since Pacemaker-2.1.0

  • enhanced support for OCF Resource Agent API 1.1 standard
    • ocf:pacemaker:attribute and ocf:pacemaker:ping agents now support 1.1
    • tools: crm_resource passes output format to agents so they will use it if supported
    • tools: crm_resource --validate and --force-check options accept optional check level to pass to agent
  • tools: crm_mon XML output includes stonith-timeout-ms and priority-fencing-delay-ms cluster properties
  • pacemakerd: support --output-as/--output-to options including XML output with interactive options such as --features

Fixes since Pacemaker-2.1.0

  • pacemaker-attrd: avoid repeated unfencing of remote nodes when DC joined cluster after remote was up
  • controller: ensure newly joining node learns the node names of non-DCs
  • controller: ensure lost node's transient attributes are cleared without DC
  • scheduler: avoid invalid transition when group member is unmanaged (CLBZ#5423)
  • scheduler: don't schedule probes of unmanaged resources on pending nodes
  • executor: avoid crash after TLS connection errors (regression introduced in 2.0.4)
  • fencing: avoid repeated attempts to get (nonexistent) meta-data for watchdog device (regression introduced in 2.1.0)
  • fencing: select correct device when pcmk_host_check="dynamic-list" and pcmk_host_map are both specified (CLBZ#5474)
  • tools: crm_attribute supports node attribute values starting with a '-' again (regression introduced in 2.1.0)
  • tools: crm_attribute deprecated --get-value option does not require an argument (regression introduced in 2.1.0)
  • tools: avoid crm_mon memory leaks when filtering by resource or node (regressions introduced in 2.0.4 and 2.0.5)
  • tools: crm_mon should show active unmanaged resources on offline nodes without requiring -r/--inactive
  • tools: better crm_resource error messages for unsupported resource types
  • tools: crm_simulate --show-failcounts includes all relevant information
  • tools: crm_mon should not show inactive group members without --inactive
  • tools: crm_mon XML output should show members of cloned groups
  • libcrmcommon: correctly handle case-sensitive XML IDs

Public API changes since Pacemaker-2.1.0

  • libcrmcommon: add pcmk_section_e type
  • libcrmcommon: add pcmk_show_opt_e type
  • libcrmcommon: add pcmk_pacemakerd_api_shutdown()
  • libpe_status: deprecate enum pe_print_options

Pacemaker 2.1.1 - Release Candidate 3

16 Aug 17:33
Compare
Choose a tag to compare
Pre-release
  • Fixes since Pacemaker-2.1.1-rc2
    • controller: ensure lost node's transient attributes are cleared without DC
    • controller: ensure newly joining node learns the node names of non-DCs

Pacemaker 2.1.1 - Release Candidate 2

06 Aug 14:59
a64ad22
Compare
Choose a tag to compare
Pre-release
  • Fixes since Pacemaker-2.1.1-rc1
    • fencer: avoid repeated attempts to get (nonexistent) meta-data for watchdog device (regression in 2.1.0)
    • tools: avoid crm_mon memory leaks when filtering by resource or node
    • tools: crm_mon should show active unmanaged resources on offline nodes without requiring -r/--inactive

Pacemaker 2.1.1 - Release Candidate 1

27 Jul 16:32
Compare
Choose a tag to compare
Pre-release
  • Features added since Pacemaker-2.1.0

    • enhanced support for OCF Resource Agent API 1.1 standard
      • ocf:pacemaker:attribute and ocf:pacemaker:ping agents now support 1.1
      • tools: crm_resource passes output format to agents so they will use it if
        supported
      • tools: crm_resource --validate and --force-check options accept optional
        check level to pass to agent
    • tools: crm_mon XML output includes stonith-timeout-ms and
      priority-fencing-delay-ms cluster properties
    • pacemakerd: support --output-as/--output-to options including XML output
      with options such as --features
  • Fixes since Pacemaker-2.1.0

    • pacemaker-attrd: avoid repeated unfencing of remote nodes when DC joined
      cluster after remote was up
    • scheduler: avoid invalid transition when group member is unmanaged
      (CLBZ#5423)
    • scheduler: don't schedule probes of unmanaged resources on pending nodes
    • fencing: select correct device when pcmk_host_check="dynamic-list" and
      pcmk_host_map are both specified (CLBZ#5474)
    • tools: crm_attribute supports node attribute values starting with a '-'
      again (regression introduced in 2.1.0)
    • tools: crm_attribute deprecated --get-value option does not require an
      argument (regression introduced in 2.1.0)
    • tools: better crm_resource error messages for unsupported resource types
    • tools: crm_simulate --show-failcounts includes all relevant information
    • tools: crm_mon should not show inactive group members without --inactive
    • tools: crm_mon XML output should show members of cloned groups
    • libcrmcommon: correctly handle case-sensitive XML IDs
  • Public API changes since Pacemaker-2.1.0

    • libcrmcommon: add pcmk_section_e type
    • libcrmcommon: add pcmk_show_opt_e type
    • libcrmcommon: add pcmk_pacemakerd_api_shutdown()
    • libpe_status: deprecate enum pe_print_options

Pacemaker 2.1.0 - Final

08 Jun 17:02
Compare
Choose a tag to compare

Release info

  • Changesets: 849
  • Diff: 327 files changed, 22089 insertions(+), 12633 deletions(-)

Known regressions introduced in this release

  • crm_mon crashes on some platforms when the fencer connection is lost in interactive mode (fixed in 2.1.8)
  • crm_resource --list-operations shows pending operations as complete (fixed in 2.1.5)
  • API: Deprecated XML_CIB_TAG_MASTER constant is unusable (fixed in 2.1.5)
  • A circular library dependency was introduced in the build process (fixed in 2.1.3)
  • The fencer can leak memory when broadcasting history differences (fixed in 2.1.3)
  • The ocf:pacemaker:Stateful resource agent has incorrect syntax in its meta-data (fixed in 2.1.3)
  • pkg-config returns the incorrect value for ocfdir (fixed in 2.1.2)
  • The fencer will make repeated attempts to get (nonexistent) meta-data for the watchdog device (fixed in 2.1.1)
  • crm_attribute with --node localhost can crash or fail due to a use-after-free error
  • crm_attribute stopped supporting node attribute values starting with a '-' (fixed in 2.1.1)
  • crm_attribute deprecated --get-value option incorrectly required an argument (fixed in 2.1.1)
  • The crm_attribute --version option incorrectly exits with status 64 instead of 0 (fixed in 2.1.1)

Features added since Pacemaker-2.0.5

  • support for OCF Resource Agent API 1.1 standard
    • allow Promoted and Unpromoted role names in CIB (in addition to Master and Slave, which are deprecated), and use new role names in output, logs, and constraints created by crm_resource --ban
    • advertise 1.1 support to agents, and provide notify_promoted_* and notify_unpromoted_* environment variables to agents with notify actions
    • support "reloadable" parameter attribute and "reload-agent" action in agents that advertise 1.1 support
    • support 1.1 standard in ocf:pacemaker:Dummy, ocf:pacemaker:remote, and ocf:pacemaker:Stateful resource agents
    • add "promoted-only" (in addition to "master-only", which is deprecated) in crm_mon XML output for bans
  • support for noncritical resources
    • colocation constraints accept an "influence" attribute that determines whether dependent influences main resource's location (the default of "true" preserves the previous behavior, while "false" makes the dependent stop if it reaches its migration-threshold in failures rather than cause both resources to move to another node)
    • resources accept a "critical" meta-attribute that serves as default for all colocation constraints involving the resource as the dependent, as well as groups involving the resource
  • detail log uses millisecond-resolution timestamps when Pacemaker is built with libqb 2.0 or later
  • CIB: deprecate the remove-after-stop cluster property, can_fail action meta-attribute, and support for Upstart-based resources
  • controller: the PCMK_panic_action environment variable may be set to sync-crash or sync-reboot to attempt to synchronize local disks before crashing or rebooting, which can be helpful to record cached log messages but runs the risk of the sync hanging and leaving the host running after a critical error
  • tools: CIB_file="-" can be used to get the CIB from standard input
  • tools: crmadmin, crm_resource, crm_simulate, and crm_verify support standard --output-as/--output-to options (including XML output, intended for parsing by scripts and higher-level tools)
  • tools: crm_attribute accepts -p/--promotion option to operate on promotion score (replacing crm_master, which is deprecated)
  • tools: crm_resource accepts --promoted option (replacing --master, which is deprecated)
  • tools: crm_resource accepts --digests advanced option
  • tools: crm_simulate accepts --show-attrs and --show-failcounts options

Build process changes since Pacemaker-2.0.5

  • Pacemaker requires newer versions of certain dependencies, including Python 3.2 or later (support for Python 2 has been dropped), glib 2.32.0 or later, libqb 0.17.0 or later, GnuTLS 2.12.0 or later (to enable Pacemaker Remote support), rpm 4.11.0 (if building RPMs), and a C library that provides setenv() and unsetenv()
  • configure: --enable-legacy-links (which is deprecated) defaults to "no", meaning that symbolic links will not be created for the Pacemaker 1 daemon names
  • configure: --enable-compat-2.0 prevents certain output changes (most significantly role names) to maintain compatibility with older tools, scripts, and resource agents that rely on previous output
  • configure: --with-resource-stickiness-default sets a resource-stickiness default in newly created CIBs
  • configure: --with-concurrent-fencing-default specifies default for concurrent-fencing cluster property
  • configure: --with-sbd-sync-default specifies default for syncing start-up with sbd
  • configure: --with-ocfrapath specifies resource agent directories to search
  • configure: --with-ocfrainstalldir specifies where to install ocf:pacemaker agents
  • configure: --with-gnutls="no" explicitly disables support for Pacemaker Remote and the remote-tls-port cluster property
  • configure: --with-acl has been removed (support for ACLs is always built)
  • configure: deprecated --with-pkgname, --with-pkg-name, --with-brand, --enable-ansi, and --enable-no-stack options have been removed
  • environment variables file (typically /etc/sysconfig/pacemaker or /etc/default/pacemaker) will be installed when "make install" is run
  • documentation has dependency on python3-sphinx instead of publican, and is generated beneath doc/sphinx

Fixes since Pacemaker-2.0.5

  • controller: always refresh agent meta-data after start, in case agent was updated (regression introduced in 1.1.18)
  • tools: avoid crash when running crm_mon in daemonized mode with CGI output (regression introduced in 2.0.3)
  • tools: correctly treat unspecified node as all nodes instead of local node when attrd_updater --query or crm_resource --cleanup is run on a Pacemaker Remote node (regressions introduced in 1.1.14 and 1.1.17)
  • pacemaker-attrd: avoid race condition where transient attributes for a leaving node could be reinstated when the node rejoins, potentially causing a node that was just rebooted to exit the cluster immediately after rejoining
  • controller,scheduler: fix year 2038 issues affecting shutdowns, remote node fencing, last-rc-change, and ticket last-granted dates
  • controller: retry scheduler connection after failure, to avoid cluster stopping on a node without stopping resources (clbz#5445)
  • fencing: avoid pending fencing entry getting "stuck" in history if originating node was unreachable when result was received
  • fencing: retry getting agent meta-data if initial attempt fails
  • fencing: detect when devices have been removed from configuration
  • scheduler: constrain clone-min, clone-max, clone-node-max, promoted-max, and promoted-node-max options to non-negative values
  • scheduler: constrain resource priorities and node-health-base to score range
  • scheduler: treat invalid duration fields in time-based rules as 0, not -1
  • scheduler: node attribute rule expressions with a value-source of "param" or "meta" work when rsc or rsc-pattern with an inverted match is given, as well as when rsc-pattern with a regular match is given
  • scheduler: node attribute rule expressions with a value-source of "param" work with a resource parameter that itself is determined by a node attribute rule expression
  • scheduler: avoid remote connection shutdown hanging when connection history for node hosting connection is not last in CIB status
  • scheduler: route monitor cancellations behind moving remote connections correctly
  • libcrmcommon: avoid potential integer overflow when adding seconds to times
  • tools: cibsecret syncs to remote nodes and guest nodes as well as cluster nodes
  • tools: show other available cluster information in crm_mon even if fence history is not available
  • tools: retry failed fencer and CIB connections in crm_mon
  • tools: crm_mon reports if Pacemaker is waiting for sbd at start-up
  • tools: respect rules when showing node attributes in crm_mon
  • tools: improve messages when crm_mon is run on disconnected remote node
  • tools: constrain node IDs to non-negative values for crm_node -N
  • tools: crm_node -l on restarted node works even when Corosync 2 is used without node names specified in Corosync configuration
  • tools: fix issues in calculation of non-sensitive resource parameter digests that made crm_simulate wrongly think configuration changed

C API changes since Pacemaker-2.0.5

  • all: new PCMK_ALLOW_DEPRECATED constant controls API availability
  • libcrmcluster: deprecate crm_terminate_member()
  • libcrmcluster: deprecate crm_terminate_member_no_mainloop()
  • libcrmcommon: add CRMD_ACTION_RELOAD_AGENT string constant
  • libcrmcommon: add PCMK_OCF_MAJOR_VERSION string constant
  • libcrmcommon: add PCMK_OCF_MINOR_VERSION string constant
  • libcrmcommon: add PCMK_OCF_RUNNING_PROMOTED enum value
  • libcrmcommon: add PCMK_OCF_VERSION string constant
  • libcrmcommon: add PCMK_XE_PROMOTABLE_LEGACY string constant
  • libcrmcommon: add PCMK_XE_PROMOTED_MAX_LEGACY string constant
  • libcrmcommon: add enum ocf_exitcode (moved from libcrmservice)
  • libcrmcommon: deprecate __builtin_expect()
  • libcrmcommon: deprecate __likely()
  • libcrmcommon: deprecate __unlikely()
  • libcrmcommon: deprecate crm_atoi()
  • libcrmcommon: deprecate crm_build_path()
  • libcrmcommon: deprecate crm_config_error global variable
  • libcrmcommon: deprecate crm_config_warning global variable
  • libcrmcommon: deprecate crm_ftoa()
  • libcrmcommon: deprecate crm_hash_table_size()
  • libcrmcommon: deprecate crm_itoa()
  • libcrmcommon: deprecate crm_itoa_stack()
  • libcrmcommon: deprecate crm_log_cli_init()
  • libcrmcommon: deprecate crm_parse_int()
  • libcrmcommon: deprecate crm_par...
Read more

Pacemaker 2.1.0 - Release Candidate 3

01 Jun 17:29
Compare
Choose a tag to compare
Pre-release
  • Fixes since Pacemaker-2.1.0-rc2
    • tools: avoid "error: OK" messages from crm_resource (regression in rc1)
    • tools: get crm_verify --xml-pipe/-p working again (regression in rc1)

Pacemaker 2.1.0 - Release Candidate 2

19 May 22:27
Compare
Choose a tag to compare
Pre-release
  • Features added since Pacemaker-2.1.0-rc1

    • build: configure option to specify resource agent directories to search
    • build: configure option to specify where to install ocf:pacemaker agents
    • build: configure option to specify default for syncing start-up with sbd
    • tests: improve compatibility with recent dependency versions
  • Fixes since Pacemaker-2.1.0-rc1

    • fencing: register/remove the watchdog device
    • pacemakerd: work around bug in Corosync 3.1.1/3.1.2
    • Pacemaker Remote: improve log messages

Pacemaker 2.1.0 - Release Candidate 1

30 Apr 20:16
Compare
Choose a tag to compare
Pre-release
  • Changesets: 781

  • Diff:
    323 files changed, 21034 insertions(+), 12145 deletions(-)

  • Features added since Pacemaker-2.0.5

    • support for OCF Resource Agent API 1.1 standard
      • allow Promoted and Unpromoted role names in CIB (in addition to Master
        and Slave, which are deprecated), and use new role names in output,
        logs, and constraints created by crm_resource --ban
      • advertise 1.1 support to agents, and provide notify_promoted_* and
        notify_unpromoted_* environment variables to agents with notify actions
      • support "reloadable" parameter attribute and "reload-agent" action in
        agents that advertise 1.1 support
      • support 1.1 standard in ocf:pacemaker:Dummy, ocf:pacemaker:remote, and
        ocf:pacemaker:Stateful resource agents
      • add "promoted-only" (in addition to "master-only", which is deprecated)
        in crm_mon XML output for bans
    • support for noncritical resources
      • colocation constraints accept an "influence" attribute that determines
        whether dependent influences main resource's location (the default of
        "true" preserves the previous behavior, while "false" makes the
        dependent stop if it reaches its migration-threshold in failures rather
        than cause both resources to move to another node)
      • resources accept a "critical" meta-attribute that serves as default for
        all colocation constraints involving the resource as the dependent, as
        well as groups involving the resource
    • detail log uses millisecond-resolution timestamps when Pacemaker is built
      with libqb 2.0 or later
    • CIB: deprecate the remove-after-stop cluster property, can_fail action
      meta-attribute, and support for Upstart-based resources
    • controller: the PCMK_panic_action environment variable may be set to
      sync-crash or sync-reboot to attempt to synchronize local
      disks before crashing or rebooting, which can be helpful to
      record cached log messages but runs the risk of the sync
      hanging and leaving the host running after a critical error
    • tools: CIB_file="-" can be used to get the CIB from standard input
    • tools: crmadmin, crm_resource, crm_simulate, and crm_verify support
      standard --output-as/--output-to options (including XML output,
      intended for parsing by scripts and higher-level tools)
    • tools: crm_attribute accepts -p/--promotion option to operate on
      promotion score (replacing crm_master, which is deprecated)
    • tools: crm_resource accepts --promoted option (replacing --master, which
      is deprecated)
    • tools: crm_resource accepts --digests advanced option
    • tools: crm_simulate accepts --show-attrs and --show-failcounts options
  • Build process changes since Pacemaker-2.0.5

    • Pacemaker requires newer versions of certain dependencies, including
      Python 3.2 or later (support for Python 2 has been dropped), glib 2.32.0
      or later, libqb 0.17.0 or later, GnuTLS 2.12.0 or later (to enable
      Pacemaker Remote support), rpm 4.11.0 (if building RPMs), and a C library
      that provides setenv() and unsetenv()
    • configure: --enable-legacy-links (which is deprecated) defaults to "no",
      meaning that symbolic links will not be created for the
      Pacemaker 1 daemon names
    • configure: --enable-compat-2.0 prevents certain output changes (most
      significantly role names) to maintain compatibility with older
      tools, scripts, and resource agents that rely on previous output
    • configure: --with-resource-stickiness-default sets a resource-stickiness
      default in newly created CIBs
    • configure: --with-concurrent-fencing-default specifies default for
      concurrent-fencing cluster property
    • configure: --with-gnutls="no" explicitly disables support for
      Pacemaker Remote and the remote-tls-port cluster property
    • configure: --with-acl has been removed (support for ACLs is always built)
    • configure: deprecated --with-pkgname, --with-pkg-name, --with-brand,
      --enable-ansi, and --enable-no-stack options have been removed
    • environment variables file (typically /etc/sysconfig/pacemaker or
      /etc/default/pacemaker) will be installed when "make install" is run
    • documentation has dependency on python3-sphinx instead of publican, and is
      generated beneath doc/sphinx
  • Fixes since Pacemaker-2.0.5

    • controller: always refresh agent meta-data after start, in case agent was
      updated (regression introduced in 1.1.18)
    • tools: avoid crash when running crm_mon in daemonized mode with CGI output
      (regression introduced in 2.0.3)
    • tools: correctly treat unspecified node as all nodes instead of local node
      when attrd_updater --query or crm_resource --cleanup is run on a
      Pacemaker Remote node (regressions introduced in 1.1.14 and 1.1.17)
    • pacemaker-attrd: avoid race condition where transient attributes for a
      leaving node could be reinstated when the node rejoins,
      potentially causing a node that was just rebooted to exit
      the cluster immediately after rejoining
    • controller,scheduler: fix year 2038 issues affecting shutdowns,
      remote node fencing, last-rc-change, and
      ticket last-granted dates
    • controller: retry scheduler connection after failure, to avoid cluster
      stopping on a node without stopping resources (clbz#5445)
    • fencing: avoid pending fencing entry getting "stuck" in history if
      originating node was unreachable when result was received
    • fencing: retry getting agent meta-data if initial attempt fails
    • fencing: detect when devices have been removed from configuration
    • scheduler: constrain clone-min, clone-max, clone-node-max, promoted-max,
      and promoted-node-max options to non-negative values
    • scheduler: constrain resource priorities and node-health-base to score range
    • scheduler: treat invalid duration fields in time-based rules as 0, not -1
    • scheduler: node attribute rule expressions with a value-source of "param"
      or "meta" work when rsc or rsc-pattern with an inverted match
      is given, as well as when rsc-pattern with a regular
      match is given
    • scheduler: node attribute rule expressions with a value-source of "param"
      work with a resource parameter that itself is determined by a
      node attribute rule expression
    • scheduler: avoid remote connection shutdown hanging when connection
      history for node hosting connection is not last in CIB status
    • scheduler: route monitor cancellations behind moving remote connections correctly
    • libcrmcommon: avoid potential integer overflow when adding seconds to times
    • tools: cibsecret syncs to remote nodes and guest nodes as well as
      cluster nodes
    • tools: show other available cluster information in crm_mon even if
      fence history is not available
    • tools: retry failed fencer and CIB connections in crm_mon
    • tools: crm_mon reports if Pacemaker is waiting for sbd at start-up
    • tools: respect rules when showing node attributes in crm_mon
    • tools: improve messages when crm_mon is run on disconnected remote node
    • tools: constrain node IDs to non-negative values for crm_node -N
    • tools: crm_node -l on restarted node works even when Corosync 2 is used
      without node names specified in Corosync configuration
    • tools: fix issues in calculation of non-sensitive resource parameter
      digests that made crm_simulate wrongly think configuration changed
  • C API changes since Pacemaker-2.0.5

    • all: new PCMK_ALLOW_DEPRECATED constant controls API availability
    • libcrmcluster: deprecate crm_terminate_member()
    • libcrmcluster: deprecate crm_terminate_member_no_mainloop()
    • libcrmcommon: add CRMD_ACTION_RELOAD_AGENT string constant
    • libcrmcommon: add PCMK_OCF_MAJOR_VERSION string constant
    • libcrmcommon: add PCMK_OCF_MINOR_VERSION string constant
    • libcrmcommon: add PCMK_OCF_RUNNING_PROMOTED enum value
    • libcrmcommon: add PCMK_OCF_VERSION string constant
    • libcrmcommon: add PCMK_XE_PROMOTABLE_LEGACY string constant
    • libcrmcommon: add PCMK_XE_PROMOTED_MAX_LEGACY string constant
    • libcrmcommon: add PCMK_XE_PROMOTED_NODE_MAX_LEGACY string constant
    • libcrmcommon: add enum ocf_exitcode (moved from libcrmservice)
    • libcrmcommon: deprecate __builtin_expect()
    • libcrmcommon: deprecate __likely()
    • libcrmcommon: deprecate __unlikely()
    • libcrmcommon: deprecate crm_atoi()
    • libcrmcommon: deprecate crm_build_path()
    • libcrmcommon: deprecate crm_config_error global variable
    • libcrmcommon: deprecate crm_config_warning global variable
    • libcrmcommon: deprecate crm_ftoa()
    • libcrmcommon: deprecate crm_hash_table_size()
    • libcrmcommon: deprecate crm_itoa()
    • libcrmcommon: deprecate crm_itoa_stack()
    • libcrmcommon: deprecate crm_log_cli_init()
    • libcrmcommon: deprecate crm_parse_int()
    • libcrmcommon: deprecate crm_parse_ll()
    • libcrmcommon: deprecate crm_str_hash()
    • libcrmcommon: deprecate crm_str_table_dup()
    • libcrmcommon: deprecate crm_str_table_new()
    • libcrmcommon: deprecate crm_strcase_equal()
    • libcrmcommon: deprecate crm_strcase_hash()
    • libcrmcommon: deprecate crm_strcase_table_new()
    • libcrmcommon: deprecate crm_strip_trailing_newline()
    • libcrmcommon: deprecate crm_ttoa()
    • libcrmcommon: deprecate EOS constant
    • libcrmcommon: deprecate GListPtr type
    • libcrmcommon: deprecate g_str_hash_traditional()
    • libcrmcommon: deprecate MAX_IPC_DELAY constant
    • libcrmcommon: deprecate pcmk_format_named...
Read more

Pacemaker 1.1.24 - Final

03 Dec 15:41
3850484
Compare
Choose a tag to compare

Release info

This is the final release in the Pacemaker 1.1 series.

Known regressions introduced in this release

  • None

Changes since Pacemaker-1.1.23

  • Prevent the bypassing of ACLs by direct IPC (CVE-2020-25654)
  • PE: don't select instance to be promoted on a guest that can't run
  • PE: don't schedule a dangling migration stop if one already occurred
  • tools: crmadmin -D/--dc_lookup supports --quiet to print DC name only

Pacemaker 2.0.5 - Final

02 Dec 17:13
Compare
Choose a tag to compare

Release info

  • Changesets: 534
  • Diff: 286 files changed, 23133 insertions(+), 14626 deletions(-)

Known regressions introduced in this release

  • crm_resource crashes if given extraneous arguments (fixed in 2.1.5)
  • stonith_admin --validate returns incorrect exit status (fixed in 2.1.5)
  • crm_mon can leak memory when filtering by node (fixed in 2.1.1)
  • The --version argument to crm_resource and crmadmin can exit with status 64 instead of 0 (fixed in 2.1.0)
  • crm_node -R may not remove the node from the controller's cache (fixed in 2.1.7)

Features added since Pacemaker-2.0.4

  • configuration: Add type="integer" to rule elements, allowing for specifying 64-bit integers and specifying double-precision floating point numbers when type="number"
  • daemons: Recognize new OCF agent status codes 190 (degraded) and 191 (degraded master) to be treated as success but displayed as errors
  • sbd-integration: support SBD_SYNC_RESOURCE_STARTUP environment variable to better synchronize Pacemaker start-up and shutdown with SBD
  • scheduler: Add rule-based tests to op_defaults and rsc_defaults
  • scheduler: Add on-fail=demote and no-quorum-policy=demote recovery policies for promoted resources
  • tools: Add --resource= to filter crm_mon output for a resource
  • tools: Add -P to crmadmin to show pacemakerd status
  • tools: In cibsecret, read value to set from input (or stdin) if not specified

Fixes for regressions introduced in Pacemaker-2.0.4

  • tools: Add the node name back to bundle instances in crm_mon
  • tools: get stonith_admin --list-targets working again

Fixes for regressions introduced in Pacemaker-2.0.3

  • tools: Fix adding HTTP headers to crm_mon in daemon mode

Fixes for regressions introduced in Pacemaker-2.0.1

  • scheduler: require pre-/post-start notifications correctly

Changes since Pacemaker-2.0.4

  • Prevent the bypassing of ACLs by direct IPC (CVE-2020-25654)
  • build: Fix a build issue on Fedora s390x.
  • build: Fix python2 vs. python3 packaging problems on openSUSE Tumbleweed
  • build: Update pkgconfig files for CI testing
  • controller: avoid recovery delay when shutdown locks expire
  • controller: Log correct timeout for timed-out stonith monitor
  • fencer: avoid infinite loop if device is removed during operation
  • fencer: avoid possible use-of-NULL when parsing metadata
  • libfencing: add port or plug parameter according to metadata on validate if no pcmk_host_argument specified
  • libfencing: respect pcmk_host_argument=none on validate
  • scheduler: disallow on-fail=stop for stop operations
  • scheduler: don't schedule a dangling migration stop if one already occurred
  • scheduler: don't select instance to be promoted on a guest that can't run
  • scheduler: fix build when DEFAULT_CONCURRENT_FENCING_TRUE is set
  • scheduler: Remove pe_print_expanded_xml print option.
  • scheduler: Use pcmk_monitor_timeout as stonith start timeout
  • tools: Add management status to crm_mon's group output.
  • tools: Add "No active resources" to one case in crm_mon output.
  • tools: Allow tags and alerts in cibadmin --scope
  • tools: Avoid crm_node on Pacemaker Remote nodes failing when other executor actions are occurring
  • tools: Avoid pending fence actions getting stuck in crm_mon display
  • tools: "Connectivity is lost" may not be displayed even if the ping communication is lost
  • tools: Display stop-all-resources in crm_mon's cluster options
  • tools: don't use pssh -q option in cibsecret unless supported
  • tools: Fix adding the http-equiv header to crm_mon in daemon mode
  • tools: If a clone or group is disabled, display that in crm_mon as part of the resource's header
  • tools: crm_node -l and -p now work from Pacemaker Remote nodes
  • tools: Don't display crm_resource error messages twice
  • tools: Print inactive resources by default with crm_mon xml output
  • tools: properly detect local node name in cibsecret
  • tools: Revert some crm_resource string-related checks on variables that aren't strings
  • tools: Use bash in cibsecret
  • xml: Mark new crm_mon attributes as optional in schema