RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1646350 - Clean-up of a managed bundle or guest node resource causes unnecessary recovery [rhel-7.6.z]
Summary: Clean-up of a managed bundle or guest node resource causes unnecessary recove...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pacemaker
Version: 7.4
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: rc
: 7.6
Assignee: Ken Gaillot
QA Contact: Marian Krcmarik
URL:
Whiteboard:
Depends On: 1448467
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-05 12:36 UTC by Oneata Mircea Teodor
Modified: 2018-11-27 01:22 UTC (History)
16 users (show)

Fixed In Version: pacemaker-1.1.19-8.el7_6.1
Doc Type: Bug Fix
Doc Text:
Previously, after cleaning a failure history of a managed guest node resource or bundle container, Pacemaker would schedule a re-probe of the resource and recovery of its Pacemaker Remote connection, processed in parallel. As a consequence, Pacemaker Remote connection forced recovery of the guest node resource or bundle container when it was not necessary. With this update, the connection recovery is now scheduled after the re-probe result. As a result, in case the re-probe does not find anything wrong, the recovery does not start.
Clone Of: 1448467
Environment:
Last Closed: 2018-11-27 01:21:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2120681 0 None None None 2018-11-05 12:36:39 UTC
Red Hat Product Errata RHBA-2018:3667 0 None None None 2018-11-27 01:22:11 UTC

Description Oneata Mircea Teodor 2018-11-05 12:36:30 UTC 
This bug has been copied from bug #1448467 and has been proposed to be backported to 7.6 z-stream (EUS).
Comment 2 Ken Gaillot 2018-11-05 16:54:08 UTC 
Fixed in upstream 1.1 branch by commits a07ff46, fade228, and af4f6a1
Comment 3 Ken Gaillot 2018-11-07 21:29:32 UTC 
QA: Configure and start a cluster with a guest node and/or bundle, then run "pcs resource refresh" on the guest node resource and/or bundle resource. It would also be sufficient to force the resource to have a failure then run "pcs resource cleanup".

Before the fix, the guest node or bundle will get restarted; after the fix, it won't.
Comment 7 errata-xmlrpc 2018-11-27 01:21: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-2018:3667
Note You need to log in before you can comment on or make changes to this bug.