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.
Cause: User tries to manage constraints, attributes and other properties of grouped, cloned or multistated resources in web UI.
Consequence: In web UI were displayed only primitive resources. There was no way to set attributes, constraints and other properties separately for parent (group/clone/master-slave) resource and child (primitive) resource.
Fix: Resources are displayed in tree structure. It is possible to view and edit all resource elements (groups, clones, master-slaves, primitives) independently.
Result: User now can manage constraints, attributes and other properties of groups, clones, multistates and primitive resources independently.
We need a tree-like view of resources what were grouped, cloned, or multistated to be able to set attributes, constraints and other properties per both parent and child resource elements.
Before Fix:
[root@rh71-node1 ~]# rpm -q pcs
pcs-0.9.142-2.el7.x86_64
Resources displayed in a flat structure. When setting an attribute or a constraint to a cloned or grouped resource it is not possible to set it specifically to parent or child resource.
After Fix:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.143-1.el7.x86_64
Resources are displayed in a tree view. It is possible to edit settings of a clone, a master/slave resource and a group and settings of its child resources independently.
Before Fix:
[root@rh71-node1 ~]# rpm -q pcs
pcs-0.9.143-1.el7.x86_64
Using web UI try to create an ocf:pacemaker:Dummy resource. An ocf:heartbeat:Dummy resource is created instead.
After Fix:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.143-2.el7.x86_64
Using web UI try to create an ocf:pacemaker:Dummy resource. An ocf:pacemaker:Dummy resource is created.
Test:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.143-5.el7.x86_64
After pcsd has been stopped on one node, cluster details are properly displayed in web UI. It works also when pcsd has been stopped on two out of three nodes.
Node attributes and fence levels are displayed in web UI for both online and offline nodes.
Before Fix:
[root@rh71-node1 ~]# rpm -q pcs
pcs-0.9.143-6.el7.x86_64
Web UI reloads cluster status upon each change of cluster settings done in the UI. This can lead to loading cluster status in parallel which unnecessarily takes cluster and browser resources.
If user changes resource settings using web UI (e.g. meta attributes) and removes the last constraint of the resource while web UI is loading cluster status, the constraint will remain displayed in web UI even though the constraint was successfully removed from the cluster.
After Fix:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.143-7.el7.x86_64
If a cluster status reload is triggered in web UI while another request to refresh the cluster status is already in progress, the new request is put into a queue and run only after the previous request is finished.
Resource constraints are removed properly from web UI.
After Fix:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.143-9.el7.x86_64
It is possible to create a disabled resource using web UI.
When removing the last resource from a cluster using web UI, the resource settings are no longer displayed.
In the resources page running resources are displayed in blue color, resources with warnings are displayed in orange color, resources with errors are displayed in red color.
Create a new group of resources. Try to add another resource to the group. The group name is available in the group name select.
Create a clone resource. Add an ordering set constraint containing the primitive from the clone and some other resource. An error message is displayed stating the clone shoud be used instead of the primitive. It is possible to force the constraint creation, the constraint is then created on the primitive resource.
After Fix:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.143-10.el7.x86_64
Resource details are not displayed in a group, clone and master/slave page when switching to it quickly from a primitive resource page.
Multi-state resources are displayed as running when a status of a cluster running older version of pcs is displayed.
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/RHSA-2015-2290.html