Bug 1346852
| Summary: | [GUI] Bad Request when resource removal takes longer than pcs expects | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Radek Steiger <rsteiger> | |
| Component: | pcs | Assignee: | Ondrej Mular <omular> | |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | high | |||
| Version: | 7.3 | CC: | cfeist, cluster-maint, idevat, omular, tojeline | |
| Target Milestone: | rc | Keywords: | TestBlocker | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | pcs-0.9.152-7.el7 | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
User tries to remove multiple resources with longer stopping time using GUI.
Consequence:
Resources will be removed but error message will be displayed.
Fix:
Resources are stopped in parallel before removal.
Result:
Resources are removed and no error message is displayed.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1579911 (view as bug list) | Environment: | ||
| Last Closed: | 2016-11-03 20:58:59 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: | ||||
|
Description
Radek Steiger
2016-06-15 13:08:41 UTC
proposed fixes: https://github.com/ClusterLabs/pcs/commit/e00fd8f634a49562c96d08afb043c175ee https://github.com/ClusterLabs/pcs/commit/9321b5b9e94b3d532400ff8e2bee2db5c6 Test: Create few resources with longer stopping time. > [root@rhel7-node1 ~]# for i in {1..10}; do pcs resource create dummy$i ocf:pacemaker:Dummy op_sleep=5; done Wait until all of them will start up. Then in GUI delete these resource at once. Resources will be removed and no error message will be displayed. Before fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.151-1.el7.x86_64
[vm-rhel72-1 ~] $ for i in {1..10}; do pcs resource create dummy$i ocf:pacemaker:Dummy op_sleep=5; done
Wait until all of them will start up.
In web UI delete created resource at once. Error message appear:
"""
Unable to remove resources (Bad Request)
Error: Resource 'dummy1' does not exist.
Error: Resource 'dummy10' does not exist.
Error: Resource 'dummy2' does not exist.
Error: Resource 'dummy3' does not exist.
Error: Resource 'dummy4' does not exist.
Error: Resource 'dummy5' does not exist.
Error: Resource 'dummy6' does not exist.
Error: Resource 'dummy7' does not exist.
"""
After fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.152-3.el7.x86_64
[vm-rhel72-1 ~] $ for i in {1..10}; do pcs resource create dummy$i ocf:pacemaker:Dummy op_sleep=5; done
Wait until all of them will start up. Resources will be removed and no error message will be displayed.
additional fixes: https://github.com/ClusterLabs/pcs/commit/174378be2c1dad08098e6bcca36278a95d0c https://github.com/ClusterLabs/pcs/commit/e7f7c63a0891f60f04f0db3dd30d53f03409 Test: Create few resources with longer stopping time. > [root@rhel7-node1 ~]# for i in {1..10}; do pcs resource create delay$i Delay startdelay=0 stopdelay=25 mondelay=0; done Wait until all of them will start up. Then in GUI delete these resource at once. Resources will be removed and no error message will be displayed. If removing resources takes longer than expected (timeout expired) user is notified by alert message. Setup:
Create few resources with longer stopping time.
> [vm-rhel72-1 ~] $ for i in {1..10}; do pcs resource create delay$i Delay startdelay=0 stopdelay=25 mondelay=0; done
Before Fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.152-4.el7.x86_64
Wait until all of them will start up. Then in GUI delete these resource at once. Error "Unable to remove resources (Bad Request)" appear.
After Fix:
[vm-rhel72-1 ~] $ rpm -q pcs
pcs-0.9.152-5.el7.x86_64
Wait until all of them will start up. Then in GUI delete these resource at once. Resources will be removed and no error message will be displayed. If removing resources takes longer than expected (timeout expired) user is notified by alert message.
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-2016-2596.html |