Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Using pcsd GUI it is possible to remove resource constraints and to standby/unstandby a node.  These features do not work when managing a cluster using pcsd gui running on a machine outside of the managed cluster.

Version-Release number of selected component (if applicable):
0.9.137

How reproducible:
always

Steps to Reproduce:
1. create a cluster
2. import the cluster into gui running on a machine outside of the cluster
3. try to standby/unstandby a node of the cluster
4. try to remove a constraint defined in the cluster

Actual results:
- node standby/unstandby does not do anything
- constraint remove fails with an error: "Error removing constraint: (Bad Request )"

Expected results:
Constraint removal and node standby/unstandby work when managing a cluster from a machine that is not part of the cluster.

Upstream here:
https://github.com/feist/pcs/commit/053f63ca109d9ef9e7f0416e90aab8e140480f5b

Before Fix:
[root@rh66-node1 ~]# rpm -q pcs
pcs-0.9.138-1.el6.x86_64

Constraint removal:
Constraint is not removed and an error is displayed: Error removing constraint: (Bad Request )

Node standby / unstandby:
Click on standby / unstandby button has no effect.


After Fix:
[root@rh66-node1:~]# rpm -q pcs
pcs-0.9.139-1.el6.x86_64

Constraint removal and node standby / unstandby work when managing a cluster from a machine that is not part of the cluster.

upstream patch:
https://github.com/feist/pcs/commit/b86f2d1975b448e447abf41e946832f25e9bbb43

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1446.html