Bug 1189857

Summary: need a tree view for clones/MS/groups in the resource panel [GUI]
Product: Red Hat Enterprise Linux 7 Reporter: Radek Steiger <rsteiger>
Component: pcsAssignee: Ondrej Mular <omular>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: high    
Version: 7.1CC: cfeist, cluster-maint, jruemker, mlisik, tlavigne, tojeline
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.9.143-10.el7 Doc Type: Bug Fix
Doc Text:
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.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 09:34:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1148863, 1182119, 1198640, 1219574, 1240321    
Attachments:
Description Flags
proposed fix
none
proposed fix 2
none
proposed fix - add resource form
none
proposed fix 4 none

Description Radek Steiger 2015-02-05 16:18:19 UTC
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.

Comment 4 Radek Steiger 2015-08-10 09:31:40 UTC
*** Bug 1240321 has been marked as a duplicate of this bug. ***

Comment 5 Tomas Jelinek 2015-08-10 12:59:05 UTC
Created attachment 1061041 [details]
proposed fix

Comment 6 Tomas Jelinek 2015-08-10 12:59:27 UTC
Created attachment 1061042 [details]
proposed fix 2

Comment 7 Tomas Jelinek 2015-08-10 13:18:07 UTC
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.

Comment 9 Tomas Jelinek 2015-08-11 15:08:03 UTC
Created attachment 1061559 [details]
proposed fix - add resource form

Comment 10 Tomas Jelinek 2015-08-14 11:44:11 UTC
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.

Comment 13 Tomas Jelinek 2015-09-01 11:47:03 UTC
Created attachment 1068974 [details]
proposed fix 4

Comment 14 Tomas Jelinek 2015-09-01 11:48:35 UTC
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.

Comment 16 Tomas Jelinek 2015-09-07 09:13:49 UTC
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.

Comment 18 Tomas Jelinek 2015-09-16 13:36:52 UTC
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.

Comment 22 Tomas Jelinek 2015-09-22 11:23:30 UTC
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.

Comment 26 errata-xmlrpc 2015-11-19 09:34:44 UTC
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