8.170. pcs

Bug Fixes

BZ#1029129

The pcs utility was using an incorrect location to search for cluster node names, and the "pcs cluster standby" command therefore could not find the specified cluster node. As a a consequence, it was not possible to put cluster nodes in standby mode. With this update, pcs properly searches for node names in the /etc/cluster/cluster.conf file and putting cluster nodes in standby mode works correctly.

BZ#1025054

Previously, pcs was unable to create user ID (UID) and group ID (GID) entries in the cluster.conf file. Consequently, non-root users could not gain access to corosync.conf and therefore could not access corosync. Now, pcs support for configuring UID and GID entries in cluster.conf has been added, and non-root users can be granted access to corosync with the "pcs cluster uidgid" command.

BZ#1066927

When using the "pcs resource create" command with the "--group" option, pcs created a resource and added it to a resource group in two separate steps instead of one. Consequently, a resource that was added to a pre-existing resource group sometimes initially started on an incorrect node. With this update, pcs creates a resource in a resource group as a single step when "--group" is used, and the created resource starts on the correct node.

BZ#1019410

When adding a STONITH fencing level, pcs sometimes mistakenly detected that some nodes were not a part of a cluster . As a consequence, it was not possible to add a STONITH level unless the "--force" option was used. Now, pcs correctly determines whether a node is a part of a cluster and, as long as a valid node is used, adding a pcs STONITH level no longer requires the use of the "--force" option.

BZ#1094517

Previously, pcs did not allow the use of the following attributes for STONITH fencing agents: pcmk_reboot_action, pcmk_monitor_action, and pcmk_status_action. As a consequence, using any of these attributes when configuring a STONITH agent caused the configuration to fail. With this update, pcs correctly allows the use of the attributes and the configuration no longer fails when they are used.

BZ#1108778, BZ#1107612

The pcs utility did not properly handle clones of a group when removing resources from the cloned group. As a consequence, the "pcs resource unclone" and "pcs resource delete" commands removed only the first resource in a group when they were supposed to remove the entire resource group. With this update, pcs handles resources in cloned groups correctly and removing cloned resource groups works as expected.

BZ#1107965

Due to an error in detecting whether resource groups are managed, pcs sometimes could not delete a cloned resource group or a master or slave resource group. With this update, pcs detects the status of resource groups correctly, and deleting the mentioned resource groups proceeds normally.

BZ#1094812

Previously, pcs attempted to use the corosync.conf file when listing cluster nodes using the "pcs status nodes corosync" command. However, corosync.conf does not exist in Red Hat Enterprise Linux 6. As a consequence, "pcs status nodes corosync" failed to execute. Now, cluster nodes on Red Hat Enterprise Linux 6 are listed using the cman_tool program and the /etc/cluster/cluster.conf file, and "pcs status nodes corosync" functions correctly.

Enhancement

BZ#1035300

The pcsd daemon has been added to the pacemaker packages for Red Hat Enterprise Linux 6, which allows users to remotely start, stop, enable, or disable the cluster, and also to remotely set up the cluster configuration.