I am happy to announce the latest release of PCS, version 0.12.3.

Source code is available at:
https://github.com/ClusterLabs/pcs/archive/refs/tags/v0.12.3.tar.gz
or
https://github.com/ClusterLabs/pcs/archive/refs/tags/v0.12.3.zip

Two new commands, `pcs cluster node rename-corosync` and `pcs cluster
node rename-cib`, are introduced for renaming cluster nodes in the
corosync and CIB configuration, respectively. Previously, node renaming
required error-prone manual edits across multiple configuration files.

The commands `pcs pcsd certkey` and `pcs pcsd sync-certificates`, along
with the feature to synchronize TLS certificate-key pairs across cluster
nodes, are deprecated in this release. These commands lacked
compatibility with post-quantum cryptography, and providing this
functionality within applications is uncommon. Custom certificates can
still be used with PCS Web UI, or [custom certificates in Cockpit] can
be utilized.

Operation validation has been extended to the `pcs resource update`,
`pcs resource op add`, `pcs stonith update`, and `pcs stonith op add`
commands. Operation names are now checked against agent metadata and
option values are validated, preventing invalid operations from being
silently written to the CIB.

Complete changelog for this release:

### Added
- Commands `pcs cluster node rename-corosync` and `pcs cluster node
  rename-cib` for cluster node renaming ([RHEL-7585])
- Support for displaying secret resource attributes in `pcs config` and
  `pcs resource | stonith config` commands ([RHEL-7604])
- Add validation for cluster name length. Corosync can not process too
  long names. The maximum length is set to 256 chars to prevent this
  error.
- Add validation for operations in `pcs resource update`, `pcs resource
  op add`, `pcs stonith update`, and `pcs stonith op add` commands.
  Operation names are now validated against agent metadata, and
  operation option values are also verified ([RHEL-169571])

### Fixed
- Upgrade CIB schema version when creating a colocation constraint with
  `influence` option to be able to create such constraint ([RHEL-84511])
- Fixed a crash in `pcs resource | stonith list` commands
  ([rhbz#2458608])
- `pcs constraint config` (and its variants for each constraint type)
  now list resources in sets in the order defined in the CIB, instead of
  sorting them alphabetically ([rhbz#2461143]) ([RHEL-176475])
- Location constraints with rules can be removed using web UI (broken
  since pcs-0.12.0b1) ([RHEL-183182])
- Adding a node to a cluster now removes all cluster configuration files
  from the new node before adding it.
- Fixed validation of resource operation options `enabled`,
  `record-pending` and constraint options `require-all`, `sequential`
  and `symmetrical`. Values not accepted by CIB are no longer allowed.

### Deprecated
- Commands `pcs pcsd certkey` and `pcs pcsd sync-certificates`
  ([RHEL-149608])

### Security
- Stop accepting multipart requests in pcsd as we don't use them. This
  should boost security as there have been multiple reported
  vulnerabilities in Rack and Tornado. Since we use Tornado as a proxy
  for Rack, this also prevents future attacks on the Ruby daemon.


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

Cheers,
Michal


[custom certificates in Cockpit]: https://cockpit-project.org/guide/latest/https
[RHEL-7585]: https://issues.redhat.com/browse/RHEL-7585
[RHEL-7604]: https://issues.redhat.com/browse/RHEL-7604
[RHEL-84511]: https://issues.redhat.com/browse/RHEL-84511
[RHEL-149608]: https://issues.redhat.com/browse/RHEL-149608
[RHEL-169571]: https://redhat.atlassian.net/browse/RHEL-169571
[RHEL-176475]: https://redhat.atlassian.net/browse/RHEL-176475
[RHEL-183182]: https://redhat.atlassian.net/browse/RHEL-183182
[rhbz#2458608]: https://bugzilla.redhat.com/show_bug.cgi?id=2458608
[rhbz#2461143]: https://bugzilla.redhat.com/show_bug.cgi?id=2461143

_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Reply via email to