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 1448467 - Clean-up of a managed bundle or guest node resource causes unnecessary recovery
Summary: Clean-up of a managed bundle or guest node resource causes unnecessary recovery
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.7
Assignee: Ken Gaillot
QA Contact: Ofer Blaut
URL:
Whiteboard:
: 1638580 (view as bug list)
Depends On: 1303742
Blocks: 1203710 1646349 1646350 1647927 1707454
TreeView+ depends on / blocked
 
Reported: 2017-05-05 13:27 UTC by Klaus Wenninger
Modified: 2019-08-06 12:54 UTC (History)
15 users (show)

Fixed In Version: pacemaker-1.1.20-1.el7
Doc Type: Bug Fix
Doc Text:
Cause: After cleaning failure history of a managed guest node resource or bundle container, Pacemaker would schedule a reprobe of the resource and recovery of its Pacemaker Remote connection, processed in parallel. Consequence: The Pacemaker Remote connection recovery would force recovery of the guest node resource or bundle container, even if not needed. Fix: The connection recovery is now scheduled after getting the reprobe result. Result: If the reprobe result finds everything OK, the recovery will be avoided.
Clone Of: 1303742
: 1646349 1646350 (view as bug list)
Environment:
Last Closed: 2019-08-06 12:53:38 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 2017-05-05 13:27:20 UTC
Red Hat Product Errata RHBA-2019:2129 0 None None None 2019-08-06 12:54:08 UTC

Comment 2 Klaus Wenninger 2017-05-05 13:31:27 UTC 
using this bz to track #2 solution as of above that wouldn't require container-resource to be unmanaged while cleanup of guest-connection resource.
Comment 3 michal novacek 2017-08-04 08:45:48 UTC 
This bug seems to be the clone from 7.4 which I do not understand. Why exactly do we have this same bug in 7.5?
Comment 4 Ken Gaillot 2017-08-04 15:19:22 UTC 
In 7.4, we were able to fix the issue as long as the remote connection resource is unmanaged first.

For 7.5, we are going to see if we can avoid the issue even if the resource is still managed. There's a chance this will not be practical or will need to be bumped to 7.6, but we are going to investigate it.
Comment 5 Klaus Wenninger 2017-08-07 07:47:47 UTC 
Thanks Ken for jumping in on that...
I guess that answers your question.
For further details refer to solution #2 in the description as stated in comment #2.
Comment 7 Andrew Beekhof 2017-09-25 08:00:00 UTC 
+ Andrew Beekhof (11 minutes ago) 7abc8ec: PE: Implement probing of container remote nodes  (HEAD -> master)
+ Andrew Beekhof (3 days ago) 73ffa11: PE: Revert e21a4d00 since probing remote connections is no longer a problem
Comment 8 Klaus Wenninger 2017-11-03 14:50:12 UTC 
needs some reinvestigation in the light of the above.
Should make things easier ...
moved to rhel-7.5 because of effort constraints
Comment 9 Andrew Beekhof 2017-11-05 22:01:28 UTC 
I'd be surprised if this wasnt now fixed upstream
Comment 10 Klaus Wenninger 2017-11-10 18:18:41 UTC 
(In reply to Andrew Beekhof from comment #9)
> I'd be surprised if this wasnt now fixed upstream

Guess the relevant changes should be in rhel-7.5 as of the current build (pacemaker-1.1.18-5.el7).
Haven't dug into the logs but with that version the issue isn't solved out of the box at least.
Comment 12 Ken Gaillot 2018-10-12 14:19:49 UTC 
*** Bug 1638580 has been marked as a duplicate of this bug. ***
Comment 13 Andrew Beekhof 2018-10-15 00:24:03 UTC 
(In reply to Ken Gaillot from comment #12)
> *** Bug 1638580 has been marked as a duplicate of this bug. ***

Except bz #1638580 included a working fix
Comment 14 Ken Gaillot 2018-10-31 18:32:16 UTC 
Fixed in upstream 1.1 branch by commits a07ff46, fade228, and af4f6a1
Comment 19 errata-xmlrpc 2019-08-06 12:53:38 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:2129
Note You need to log in before you can comment on or make changes to this bug.