Bug 1257369

Summary: pcs should print the output of crm_resource from pcs resource cleanup commands
Product: Red Hat Enterprise Linux 7 Reporter: Chris Feist <cfeist>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: cluster-maint, rsteiger, tojeline
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.9.143-7.el7 Doc Type: Bug Fix
Doc Text:
Cause: User runs the 'pcs resource cleanup' command. Consequence: Pcs displays a generic message on success. Fix: Display output of the crm_resource tool which actually does the cleanup. Result: User is informed about the cleanup in detail.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 09:38:42 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:
Attachments:
Description Flags
proposed fix none

Description Chris Feist 2015-08-26 23:18:33 UTC
In the new version of pacemaker, crm_resource prints out some helpful information when cleaning up resources, this should be printed out from the 'pcs resource cleanup [resource]' commands instead of the current success message.

Comment 2 Tomas Jelinek 2015-09-04 15:14:32 UTC
Created attachment 1070322 [details]
proposed fix

Comment 3 Tomas Jelinek 2015-09-07 09:11:10 UTC
Before Fix:
[root@rh71-node1 ~]# rpm -q pcs
pcs-0.9.143-6.el7.x86_64
[root@rh71-node1:~]# pcs resource cleanup dummy
Resource: dummy successfully cleaned up



After Fix:
[root@rh71-node1:~]# rpm -q pcs
pcs-0.9.143-7.el7.x86_64
[root@rh71-node1:~]# pcs resource cleanup dummy
Waiting for 2 replies from the CRMd.. OK
Cleaning up dummy on rh71-node1
Cleaning up dummy on rh71-node2

Comment 7 errata-xmlrpc 2015-11-19 09:38:42 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