[ClusterLabs] pcs 0.10.9 released

[Miroslav Lisik]

I am happy to announce the latest release of pcs, version 0.10.9.

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

Complete change log for this release:
## [0.10.9] - 2021-08-10

### Added
- Elliptic curve TLS certificates are now supported in pcsd
   ([ghissue#123])
- Support for corosync option `totem.block_unlisted_ips`
   ([rhbz#1720221])
- Support for displaying status of a single resource or tag
   ([rhbz#1290830])
- Support for displaying status of resources on a specified node
   ([rhbz#1285269])
- New option `--brief` for `pcs resource disable --safe` or its alias
   `pcs resource safe-disable` that only prints errors ([rhbz#1909901])
- Support for updating scsi fencing devices without affecting other
   resources added in the new command `pcs stonith update-scsi-devices`
   ([rhbz#1759995], [rhbz#1872378])
- Option `--autodelete` for `pcs resource move` command which removes a
   location constraint used for moving a resource, once the resource has
   been moved. This feature is in tech-preview state and thus may be
   changed in the future ([rhbz#1847102])

### Fixed
- Node attribute expressions are now correctly reported as not allowed
   in resource defaults rules ([rhbz#1896458])
- Upgreded to jquery 3.6.0 ([rhbz#1882291, rhbz#1886342])
- Man page and help: note that 'pcs resource unclone' accepts clone
   resources as well ([rhbz#1930886])
- Improved error messages when a host is found to be a part of a cluster
   already ([rhbz#1690419])
- `pcs cluster sync` command now warns reloading corosync config is
   necessary for changes to take effect ([rhbz#1750240])
- Show user friendly error if unable to delete a group (due to the group
   being referenced within configuration) when moving resources out of
   the the group.  ([rhbz#1678273])
- Exit with an error if `on-fail=demote` is specified for a resource
   operation and pacemaker doesn't support it
- The `pcs status nodes` command now correctly shows status of nodes
   that are both in maintenance and standby modes ([rhbz#1432097])

### Changed
- python3-openssl was replaced with python3-cryptography
   ([rhbz#1927404])

### Deprecated
- `pcs acl show` replaced with `pcs acl config`
- `pcs alert show` replaced with `pcs alert config`
- Undocumented command `pcs cluster certkey` replaced with `pcs pcsd
   certkey`
- `pcs cluster pcsd-status` replaced with `pcs status pcsd` or `pcs pcsd
   status`
- `pcs constraint [location | colocation | order | ticket] show | list`
   replaced with `pcs constraint [location | colocation | order | ticket]
   config`
- `pcs property show`, `pcs property list` replaced with `pcs property
   config`
- pcsd urls: `/remote/config_backup`, `/remote/node_available`,
   `/remote/node_restart`, `/remote/resource_status`
- Undocumented syntax for constraint location rules:
   - `date start=<date> gt` replaced with `date gt <date>`
   - `date end=<date> lt` replaced with `date lt <date>`
   - `date start=<date> end=<date> in_range` replaced with `date in_range
     <date> to <date>`
   - `operation=date_spec` replaced with `date-spec <date-spec options>`
   - converting invalid score to score-attribute=pingd
- Delimiting stonith devices with a comma in `pcs stonith level add |
   clear | delete | remove` commands, use a space instead
- `pcs stonith level delete | remove [<target>] [<stonith id>]...`
   replaced with `pcs stonith level delete | remove [target <target>]
   [stonith <stonith id>]...`
- `pcs stonith level clear [<target> | <stonith ids>]` replaced with
   `pcs stonith level clear [target <target> | stonith <stonith id>...]`
- `pcs tag list` replaced with `pcs tag config`


Thanks / congratulations to everyone who contributed to this release,
including Fabio M. Di Nitto, Ivan Devat, Karolina Malyjurkova, Michal
Pospisil, Miroslav Lisik, Ondrej Mular, Tomas Jelinek.

Cheers,
Miroslav


[ghissue#123]: https://github.com/ClusterLabs/pcs/issues/123
[rhbz#1285269]: https://bugzilla.redhat.com/show_bug.cgi?id=1285269
[rhbz#1290830]: https://bugzilla.redhat.com/show_bug.cgi?id=1290830
[rhbz#1432097]: https://bugzilla.redhat.com/show_bug.cgi?id=1432097
[rhbz#1678273]: https://bugzilla.redhat.com/show_bug.cgi?id=1678273
[rhbz#1690419]: https://bugzilla.redhat.com/show_bug.cgi?id=1690419
[rhbz#1720221]: https://bugzilla.redhat.com/show_bug.cgi?id=1720221
[rhbz#1750240]: https://bugzilla.redhat.com/show_bug.cgi?id=1750240
[rhbz#1759995]: https://bugzilla.redhat.com/show_bug.cgi?id=1759995
[rhbz#1847102]: https://bugzilla.redhat.com/show_bug.cgi?id=1847102
[rhbz#1872378]: https://bugzilla.redhat.com/show_bug.cgi?id=1872378
[rhbz#1882291]: https://bugzilla.redhat.com/show_bug.cgi?id=1882291
[rhbz#1886342]: https://bugzilla.redhat.com/show_bug.cgi?id=1886342
[rhbz#1896458]: https://bugzilla.redhat.com/show_bug.cgi?id=1896458
[rhbz#1909901]: https://bugzilla.redhat.com/show_bug.cgi?id=1909901
[rhbz#1927404]: https://bugzilla.redhat.com/show_bug.cgi?id=1927404
[rhbz#1930886]: https://bugzilla.redhat.com/show_bug.cgi?id=1930886