Bug 1792492

Summary:	Rebase on latest upstream 1.1 version
Product:	Red Hat Enterprise Linux 7	Reporter:	Ken Gaillot <kgaillot>
Component:	pacemaker	Assignee:	Ken Gaillot <kgaillot>
Status:	CLOSED ERRATA	QA Contact:	cluster-qe <cluster-qe>
Severity:	high	Docs Contact:	Steven J. Levine <slevine>
Priority:	high
Version:	7.8	CC:	cfeist, cluster-maint, lkuprova, phagara
Target Milestone:	pre-dev-freeze	Keywords:	Rebase
Target Release:	7.9
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pacemaker-1.1.23-1.el7	Doc Type:	Enhancement
Doc Text:	.`pacemaker` rebased to version 1.1.23 The Pacemaker cluster resource manager has been upgraded to upstream version 1.1.23, which provides a number of bug fixes.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-29 20:03: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:

Description Ken Gaillot 2020-01-17 17:40:16 UTC

Description of problem: Rebasing on the latest upstream 1.1 version will fix at least 4 Red Hat BZs and provide a cleaner code base for backports. Currently the latest is 1.1.22, and 1.1.23 is expected in the 7.9 time frame.

Comment 2 Patrik Hagara 2020-02-21 17:58:28 UTC

qa_ack+, rebase

Comment 27 Ken Gaillot 2020-05-27 16:32:53 UTC

After further consideration of upgrade issues it would cause, the priority-fencing-delay feature will not be included in the upstream release, therefore we will not include it in RHEL, either.

Comment 28 Steven J. Levine 2020-05-27 16:36:18 UTC

I'll remove the documentation of the feature from my 7.9 GA draft, but I'll keep it in my 8.3 draft.  Also I should be able to use what we had written originally for this release note in the 8.3 release notes, either as a separate feature or as part of a general rebase description.

Comment 35 Patrik Hagara 2020-06-19 11:02:37 UTC

rebased on upstream 1.1 branch with a few backport patches

any issues found will be filed as separate BZs

marking verified

Comment 37 errata-xmlrpc 2020-09-29 20:03:57 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 (pacemaker bug fix and enhancement update), 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/RHEA-2020:3951