Bug 1469385

Summary:	Update glusterfs client rpms to the latest at RHEL 7.5
Product:	Red Hat Enterprise Linux 7	Reporter:	Atin Mukherjee <amukherj>
Component:	glusterfs	Assignee:	Milind Changire <mchangir>
Status:	CLOSED ERRATA	QA Contact:	Rahul Hinduja <rhinduja>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.5	CC:	rcyriac, vdas
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-04-10 18:48:20 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:
Bug Depends On:
Bug Blocks:	1469361

Description Atin Mukherjee 2017-07-11 07:31:07 UTC

Description of problem:

Rebase glusterfs client rpms to the latest in RHEL 7.5

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.

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 2 Milind Changire 2017-11-13 03:20:22 UTC

Changing to MODIFIED to attach builds.

Comment 4 Vivek Das 2018-03-23 07:18:23 UTC

Update to RHEL7.5 client packages are successful.
Required version of packages are updated.

Comment 8 errata-xmlrpc 2018-04-10 18:48:20 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:1010