8.141. pcs

Bug Fixes

BZ#901588

Previously, the constraint rules IDs and the resource operation IDs were not displayed in the pcs utility. As a consequence, users were unable to remove the rules using pcs and had to use other tools or edit the Cluster Information Base (CIB) directly. This update adds the "--full" option which displays the IDs for resource operations and constraint rules, and users are now able to handle the rules using pcs.

BZ#901607

Previously, the pcs utility was unable to create constraints to promote or demote master and slave resources. Consequently, it was impossible to promote or demote master and slave resources using pcs. This update adds the ability for pcs to promote or demote master and slave resources using constriants.

BZ#902450

Previously, when the user created a resource with a monitor operation and then attempted to update the monitor operation, instead of updating the monitor operation a new operation was created. Consequently, it was impossible to update resource monitor operations in the pcs utility. This bug has been fixed and updating resource monitor operations in pcs now works as expected.

BZ#902453

The pcs utility showed no error message when the user selected a non-existent resource agent while creating a resource. Consequently, the resource did not start but the user was not notified of it. This update adds an error message, which can be overridden with the "--force" flag when necessary, and users are now properly notified in case of selecting a non-existent resource agent.

BZ#902460

Previously, the pcs utility contained no specific error message when the user submitted an unrecognized option. Consequently, pcs returned a traceback instead of an error message. With this update, pcs prints a specific error message in the described scenario.

BZ#903712

The "pcs config" command did not show resources configured as master and slave resources when the configuration of the Pacemaker cluster was reviewed. Consequently, users had to directly analyze the Cluster Information Base (CIB) to view the configured master and slave resources and their options. This update provides a patch to address this bug, so the "pcs config" command now shows all resources, including master and slave resources.

BZ#912496

Prior to this update, it was impossible to specify multiple resource operations when creating a resource in the pcs utility. Consequently, only resources with one operation could be created. The "pcs resource create" command has been updated and users are now able to create resources with multiple operations.

BZ#912498

Previously, when a resource had multiple operations, they were all displayed on the same line. Consequently, it was difficult to see all operations of a particular resource. With this update, each resource operation is displayed on its own line.

BZ#912528

Previously, the pcs utility did not contain a command for cleaning up resource failures. Consequently, users were unable to clean up the failed resources. This update adds the "pcs resource cleanup" command to solve this problem.

BZ#915248

Previously, the pcs utility did not support checking or resetting failure counts of a resource. As a consequence, users had to use other unsupported tools instead. With this update, users can reset and view failure counts for the specific resources using the "pcs resource failcount show" and "pcs resource failcount reset" commands.

BZ#916993

Prior to this update, the pcs utility had no manual page. As a consequence, users had to use the "pcs --help" command instead of viewing a manual page. The pcs(8) manual page has been added and users can now view full documentation for pcs using the "man pcs" command.

BZ#920767

Previously, the pcs utility did not contain support for managing or unmanaging resource groups. Consequently, users were allowed to manage and unmanage only individual resources. This update adds the necessary support and users can now manage and unmanage entire groups of resources.

BZ#998970

Previously, removing a group containing resources did not work correctly in the pcs utility. Consequently, the group was removed, but the resources remained. This bug has been fixed and the "pcs resource delete <groupname>" command now properly deletes both the group and the resources it contains.

Enhancement

BZ#887926

This update adds support for editing cluster configuration with a standard editor to the pcs utility. This will save the user several steps, including saving the Cluster Information Base (CIB), editing it, and then pushing it back to the cluster. Users can edit and update the cluster configuration in one step using the "pcs cluster edit" command.