Skip to content

Releases: ClusterLabs/pcs

pcs-0.12.2

14 Jan 17:03

Choose a tag to compare

The 0.12.2 release adds a new ‘--no-stop’ flag for deleting resources. This separates the action of skipping stopping of resources before deletion from overriding validation errors, which is the current combined behavior of the ‘--force’ flag. For instance, when removing the last fence device, PCS suggests using ‘--force’ to bypass the validation error, not mentioning the side effect of not stopping the device. Now, you can use ‘"--future --force’" to only bypass validation errors while still stopping resources before deletion. Note that nothing changes in the ‘--force’ flag behavior for now, but in the next major version, ‘--force’ will not skip stopping of resources before deletion.

Other notable improvements also include verifying meta attribute names when updating primitive resources to avoid misconfiguration. Additionally, adding descriptions to CIB elements is now possible via new commands ‘pcs cib element description’, with a shortcut for resources - ‘pcs resource|stonith description’.

Changelog

Added

  • Commands pcs resource|stonith|booth delete|remove and pcs cluster node delete-remote|remove-remote|delete-guest|remove-guest now warn about omitting live cluster actions when '-f' is used (RHEL-76157)
  • Command pcs cib element description to manage descriptions of CIB elements, and aliases pcs resource|stonith description (RHEL-7670)
  • Commands pcs resource|stonith create, pcs resource|stonith meta and pcs resource|stonith defaults print warning about primitive resource meta attributes which have no effect on cluster resource handling (RHEL-7673)
  • Warning when Corosync configuration fails to reload (RHEL-47300)
  • Added warning that setting cluster property stonith-enabled to a falsy value can leave the cluster with no enabled means to fence nodes (RHEL-84120)

Fixed

  • Commands pcs acl role create and pcs acl permission add now print specific error messages in case of invalid input instead of command usage
  • Do not display a warning in pcs status when a fence_heuristics_ping stonith device has its method option set to cycle (RHEL-73527)
  • Add missing check to prevent the root user to run pcs client local-auth command
  • Setting ping_interval and ping_timeout knet options to less than 200ms is no longer allowed to prevent cluster misconfiguration (RHEL-21879)
  • Prevent an unhandled exception when accessing pcsd /remote/... urls on nodes with an invalid local corosync configuration

Changed

  • Lib command cib.remove_elements does not stop resources before deletion. The resources should be stopped before calling this command
  • Commands pcs resource|booth delete|remove and pcs cluster node delete-remote|remove-remote will now end with an error when trying to delete unmanaged started resources (RHEL-76162)
  • Do not wrap resource and stonith agent description to preserve existing formatting (RHEL-111451)

Deprecated

  • Using --force in pcs resource|booth delete|remove and pcs cluster node delete-remote|remove-remote to skip resource stopping before their deletion. Use the new --no-stop flag instead. You can use --future flag if you need to use --force and you do not wish to skip the resource stopping.
  • Value sctp of the knet link option transport is deprecated in corosync / knet and might be removed in a future release (RHEL-126839)

Thanks / congratulations to everyone who contributed to this release, including Ivan Devat, Michal Pospíšil, Miro Hrončok, Miroslav Lisik, Peter Romančík and Tomas Jelinek.

pcs-0.11.11

14 Jan 17:01

Choose a tag to compare

The 0.11 series is only getting a minor update as the development focuses more on the 0.12 branch. Therefore it doesn't need a separate announcement, as it contains only a few fixes backported from the 0.12.1 release.

Changelog

Changed

  • Do not wrap resource and stonith agent description to preserve existing formatting (RHEL-113763)

Fixed

  • Prevent an unhandled exception when accessing pcsd /remote/... urls on nodes with an invalid local corosync configuration

Deprecated

  • Value sctp of the knet link option transport is deprecated in corosync / knet and might be removed in a future release (RHEL-126842)

Thanks / congratulations to everyone who contributed to this release, including Ivan Devat, Michal Pospíšil, Miroslav Lisik, Peter Romancik and Tomas Jelinek.

pcs-0.11.10

17 Jul 16:51

Choose a tag to compare

This is a backport of the 0.12.1 release.

Complete change log for this release:

Added

  • Commands pcs cluster cib-push and pcs cluster edit now print more info when new CIB does not conform to the CIB schema (RHEL-76059)
  • Commands pcs cluster cib-push and pcs cluster edit now print info about problems in pushed CIB even if it conforms to the CIB schema (RHEL-76060)
  • Command pcs stonith sbd watchdog list now prints watchdogs' identity and driver (RHEL-76177)
  • Command pcs cluster rename for changing cluster name (RHEL-76055)
  • Prevent removing or disabling stonith devices or disabling SBD if the cluster would be left with disabled SBD and no stonith devices (RHEL-76170)
  • Support for exporting alerts in json and cmd formats (RHEL-76153)
  • Output of pcs status now contains messages about CIB misconfiguration provided by crm_verify pacemaker tool (RHEL-76060)
  • Support for bundle resources in pcs resource meta, disallow updating remote-node and remote-addr without --force, add lib command resource.update_meta to API v2 (RHEL-35420)
  • Support for exporting node attributes and utilization in json and cmd formats (RHEL-76154)
  • Support for reading sate and logs directories from systemd environment variables STATE_DIRECTORY and LOGS_DIRECTORY (RHEL-97220)

Fixed

  • Fixed a traceback when removing a resource fails in web UI
  • It is now possible to override errors when editing cluster properties in web UI
  • Display node-attribute in colocation constraints configuration (RHEL-82894)
  • Fixed cluster status parsing when the target-role meta attribute is not properly capitalized as defined by pacemaker specification. Affected commands:
    • pcs resource|stonith delete|remove, pcs booth delete|remove, and pcs cluster node delete-remote|remove-remote (broken since 0.11.9) (RHEL-92044)
    • pcs status query resource (broken since 0.11.8)
  • Handle query limit errors coming from rubygem-rack (RHEL-90151)

pcs-0.12.1

17 Jul 13:47

Choose a tag to compare

This release contains a regression fix for commands that delete resources, booth resources, stonith devices and remote nodes. The commands would fail when capitalization of target-role meta attribute value didn't follow the Pacemaker specification. The booth command has been broken since 0.12.0 and the remaining commands since 0.12.0b1.

On the news functionality front, pcs now allows you to rename clusters with the new cluster rename command. Also, exporting cluster configuration was further expanded to alerts, node utilization and attributes.

Configuration errors not caught by the CIB schema are now easier to spot as pcs runs additional CIB checks in cluster cib-push and cluster edit commands. These warnings are now also part of the pcs status output.

The resource meta and stonith meta commands were fully reimplemented. The resource meta command also now supports bundle resources. Additional checks were added to prevent inadvertent updates of remote-node and remote-addr meta attributes.

Complete change log for this release:

Added

  • Commands pcs cluster cib-push and pcs cluster edit now print more info when new CIB does not conform to the CIB schema (RHEL-63186)
  • Commands pcs cluster cib-push and pcs cluster edit now print info about problems in pushed CIB even if it conforms to the CIB schema (RHEL-7681)
  • Command pcs cluster rename for changing cluster name (RHEL-22423)
  • Command pcs stonith sbd watchdog list now prints watchdogs' identity and driver (RHEL-76176)
  • Prevent removing or disabling stonith devices or disabling SBD if the cluster would be left with disabled SBD and no stonith devices (RHEL-66607)
  • Support for exporting alerts in json and cmd formats (RHEL-44347)
  • Output of pcs status now contains messages about CIB misconfiguration provided by crm_verify pacemaker tool (RHEL-7681)
  • Support for bundle resources in pcs resource meta, disallow updating remote-node and remote-addr without --force, add lib command resource.update_meta to API v2 ([RHEL-35407])
  • Support for exporting node attributes and utilization in json and cmd formats (RHEL-21050)
  • Support for reading sate and logs directories from systemd environment variables STATE_DIRECTORY and LOGS_DIRECTORY (RHEL-96074)

Fixed

  • Fixed a traceback when removing a resource fails in web UI
  • It is now possible to override errors when editing cluster properties in web UI
  • Display node-attribute in colocation constraints configuration (RHEL-81938)
  • Fixed cluster status parsing when the target-role meta attribute is not properly capitalized as defined by pacemaker specification. Affected commands:
    • pcs resource|stonith delete|remove, pcs booth delete|remove, and pcs cluster node delete-remote|remove-remote (broken since 0.12.0) (RHEL-92043)
    • pcs status query resource (broken since 0.12.0)
  • Handle query limit errors coming from rubygem-rack (RHEL-90151)

pcs-0.12.0.2

29 Apr 16:40

Choose a tag to compare

We're sorry for publishing the 0.12.0.1 release without one of the tests that was mistakenly removed during cherry-picking. Functionally, there is nothing wrong with the release, the missing test however causes the automated test suite to fail. This release fixes that issue.

Special thank you goes to @vvidic for alerting us about the issue.

Complete change log for this release:

Fixed

  • Fixed failing test in the 0.12.0.1 tarball

Known Issues

  • pcs resource|stonith delete|remove, pcs status query resource, pcs booth delete|remove and pcs cluster node delete-remote|remove-remote commands will fail if target-role meta attribute is not capitalized according to Pacemaker's specification (broken since 0.12.0, fixed in 0.12.1)

pcs-0.12.0.1

15 Apr 11:15

Choose a tag to compare

Two regressions were found, both concerning bundle resources. This release also fixes issues with installing and uninstalling pcs from source introduced in 0.12.0b1. Please, refer to the changelog below for details.

Complete change log for this release:

Fixed

  • Command pcs resource restart allows restarting bundle instances (broken since pcs-0.12.0b1) (RHEL-79033)
  • Do not end with traceback when using pcs resource delete to remove bundle resources when the bundle has no IP address specified (RHEL-79090)
  • Make install no longer fails on systems with merged /usr/sbin and /usr/bin

pcs-0.11.9.1

15 Apr 11:18

Choose a tag to compare

Two regressions were found, both concerning bundle resources. Please, refer to the changelog below for details.

Complete change log for this release:

Fixed

  • Command pcs resource restart allows restarting bundle instances (broken
    since pcs-0.11.9) (RHEL-79055)
  • Do not end with traceback when using pcs resource delete to remove bundle
    resources when the bundle has no IP address specified (RHEL-79160)

Known Issues

  • pcs resource|stonith delete|remove, pcs status query resource, pcs booth delete|remove and pcs cluster node delete-remote|remove-remote commands will fail if target-role meta attribute is not capitalized according to Pacemaker's specification (broken since 0.11.9, fixed in 0.11.10)

pcs-0.11.9

17 Jan 14:41

Choose a tag to compare

As this release was developed alongside a new major version release, it brings a lot of fixes and new features. It also continues with deprecations for Pacemaker 3 that started in the previous version (0.11.8).

The pcs resource delete command gained the ability to delete tags and multiple resources at once. It has been completely rewritten so it should also be faster and provide more informative output.

Ability to export configuration as commands or in json format was extended to stonith levels and tags.

Complete change log for this release:

Added

  • Support for output formats json and cmd to pcs tag config command (RHEL-46284)
  • Command resource.restart in API v2
  • Add lib commands cluster.get_corosync_conf_struct and resource.get_configured_resources to API v2
  • Add lib command status.full_cluster_status_plaintext to API v1 (RHEL-61738)
  • Lib command cib.remove_elements can now remove resources
  • Support for exporting stonith levels in json and cmd formats in commands pcs stonith config and pcs stonith level config commands (RHEL-16232)
  • Pkg-config with info for webui is now provided.
  • Commands pcs booth ticket standby, pcs booth ticket unstandby, and pcs booth ticket cleanup which allow for managing the state of the ticket (RHEL-69040)

Changed

  • Commands pcs resource delete | remove and pcs stonith delete | remove now allow (RHEL-61901):
    • deletion of multiple resources or stonith resources with one command
    • deletion of resources or stonith resources included in tags

Fixed

  • Do not end with error when using the instances quantifier in pcs status query resource is-state command (RHEL-55441)
  • Do not display a warning in pcs status when a fence_sbd stonith device has its method option set to cycle (RHEL-46286)
  • Do not display expired constraints in pcs constraint location config resources unless --all is specified (RHEL-46293)
  • Displaying status of local and remote cluster sites in pcs dr status command. (RHEL-61738)
  • Specify the meaning of zero value timeout in pcs status wait (RHEL-46303)

Deprecated

  • Using pcs resource delete | remove to delete resources representing remote and guest nodes. Use pcs cluster node remove-remote and pcs cluster node remove-guest instead.
  • Commands pcs constraint rule add | delete | remove, as support for multiple rules in a location constraint is among the features planned to be removed in pacemaker 3

pcs-0.12.0

14 Jan 16:58

Choose a tag to compare

There have not been many changes since the last beta. Please remember, that most changes were done in the pre-releases, so check out the previous releases to see all of the changes:
https://github.com/ClusterLabs/pcs/releases/tag/v0.12.0b1
https://github.com/ClusterLabs/pcs/releases/tag/v0.12.0a1

Complete change log for this release:

Added

  • Command pcs booth ticket cleanup that enables removal of booth tickets still loaded in CIB after their removal from booth configuration (RHEL-7602)
  • Commands pcs booth ticket standby and pcs booth ticket unstandby which allow for managing the state of the ticket (RHEL-12709)

Fixed

  • Specify the meaning of zero value timeout in pcs status wait (RHEL-44719)

pcs-0.10.19

18 Dec 16:00

Choose a tag to compare

This is a special release of the no longer maintained pcs-0.10 branch. It includes security hardening for recently reported vulnerabilities related to processing HTTP headers in multiple rubygems. In addition, the last published release was not able to produce RPMs with make rpm. Special thank you goes to S Sathish S for alerting us about this issue.

Complete change log for this release:

Security

  • HTTP headers are no longer resent from Python daemon to the Ruby daemon. This is security hardening against vulnerabilities in rubygems Puma, Rack and Sinatra that have been recently reported.

Fixed

  • Failure to build pcs from upstream specfile from a tagged commit. The only affected release is 0.10.18.