Bug 1198274
Summary: | pcsd: don't automatically use --force everytime a resource is being removed | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Radek Steiger <rsteiger> | ||||
Component: | pcs | Assignee: | Tomas Jelinek <tojeline> | ||||
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | ||||
Severity: | unspecified | Docs Contact: | Steven J. Levine <slevine> | ||||
Priority: | high | ||||||
Version: | 7.1 | CC: | cluster-maint, slevine, tojeline | ||||
Target Milestone: | rc | Keywords: | Regression | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | pcs-0.9.141-1.el7 | Doc Type: | Bug Fix | ||||
Doc Text: |
Cause:
User removes a resource from a cluster using Web UI.
Consequence:
The resource is removed from the cluster without being stopped first.
Fix:
Add an option to specify whether the resource should be stopped before it is removed from the cluster.
Result:
By default the resource is stopped before it is removed from the cluster. User can remove the resource without stopping it first by checking a checkbox in Resource Removal dialog.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-11-19 09:35:57 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: | 1205796 | ||||||
Attachments: |
|
Description
Radek Steiger
2015-03-03 17:17:24 UTC
Created attachment 1037335 [details]
proposed fix
Test:
There is a checkbox in the Resource Removal dialog which controls the --force flag of the 'pcs resource remove' command. When the checkbox is empty, pcs will wait for the removed resource to stop, otherwise it will delete the resource without stopping it first.
Before Fix: [root@rh71-node1 ~]# rpm -q pcs pcs-0.9.140-1.el7.x86_64 [root@rh71-node1:~]# pcs resource create delay delay startdelay=0 stopdelay=10 Delete the delay resource using web UI, then immediately: [root@rh71-node1:~]# pcs resource delay (ocf::heartbeat:Delay): ORPHANED Started rh71-node1 After Fix: [root@rh71-node1:~]# rpm -q pcs pcs-0.9.141-1.el7.x86_64 [root@rh71-node1:~]# pcs resource create delay delay startdelay=0 stopdelay=10 Delete the delay resource using web UI, a dialog is displayed asking if you want to force the deletion. If you do not enforce it the resource is stopped first and then deleted. 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 |