Bug 1820603

Summary:	Update the glusterfs client rpms at RHEL 8.2.1 to higher version available at RHGS
Product:	Red Hat Enterprise Linux 8	Reporter:	Sunil Kumar Acharya <sheggodu>
Component:	glusterfs	Assignee:	Rinku <rkothiya>
Status:	CLOSED ERRATA	QA Contact:	Vivek Das <vdas>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.2	CC:	asabadra, jwboyer, pprakash, rcyriac
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	8.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0-37	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-21 14:30:43 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 Sunil Kumar Acharya 2020-04-03 12:47:11 UTC

Description of problem:

Update the glusterfs client rpms at RHEL 8.2.1 to higher rebased version available at RHGS

Reasons for request:

The glusterfs native client is being re-based/refreshed at every RHEL minor release as it's fast-changing and typically has a lot of stability fixes, performance and other enhancements every 6 - 7 months that we like to deliver to our customers.

It is also recommended that the RHGS servers and clients stay at the same versions, and this requires the glusterfs native client at RHEL to be regularly updated.

The RHGS server is being rebased to a higher upstream version (glusterfs-6.0) at RHGS 3.5.0 release, and so the glusterfs client at RHEL7 needs to be updated to the same rebased version.

If we do not do this, the glusterfs client in RHEL will get very stale and will generate un-needed escalations and support issues. This process has been followed for the past years with great success delivering the latest and greatest to our customers. This way we also avoid re-base requests during z-streams which is always an exception.

Comment 20 errata-xmlrpc 2020-07-21 14:30:43 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-2020:3039