Bug 1664242

Summary: Refreshing an unmanaged resource does not clean up its state entirely [rhel-7.6.z]
Product: Red Hat Enterprise Linux 7 Reporter: RAD team bot copy to z-stream <autobot-eus-copy>
Component: pacemakerAssignee: Ken Gaillot <kgaillot>
Status: CLOSED ERRATA QA Contact: Marian Krcmarik <mkrcmari>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.6CC: abeekhof, cluster-maint, mjuricek, msuchane
Target Milestone: rcKeywords: Regression, ZStream
Target Release: 7.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pacemaker-1.1.19-8.el7_6.3 Doc Type: Bug Fix
Doc Text:
Previously, the "pcs resource refresh" command or the "pcs resource cleanup" command with a failed resource sometimes failed to wait for results from all nodes. As a consequence, those resources were not cleaned on all nodes. With this update, the problem has been fixed, and Pacemaker now cleans resources on all nodes.
Story Points: ---
Clone Of: 1652053 Environment:
Last Closed: 2019-01-29 17:24:58 UTC Type: ---
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: 1652053    
Bug Blocks:    

Description RAD team bot copy to z-stream 2019-01-08 08:03:54 UTC
This bug has been copied from bug #1652053 and has been proposed to be backported to 7.6 z-stream (EUS).

Comment 3 Ken Gaillot 2019-01-08 18:11:01 UTC
QA: See parent bug description for reproducer. An alternative would be to make a resource fail on all nodes in a multi-node cluster, then run "pcs resource cleanup <rsc_id>", and seeing whether all failures were cleaned.

Comment 6 errata-xmlrpc 2019-01-29 17:24:58 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://access.redhat.com/errata/RHBA-2019:0196