Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1657140 - Update glusterfs client rpms to the latest at RHEL 7.7
Summary: Update glusterfs client rpms to the latest at RHEL 7.7
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glusterfs
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Milind Changire
QA Contact: Vivek Das
URL:
Whiteboard:
Depends On:
Blocks: 1657156
TreeView+ depends on / blocked
 
Reported: 2018-12-07 08:26 UTC by Sunil Kumar Acharya
Modified: 2019-08-06 13:01 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.12.2-44
Doc Type: If docs needed, set a value
Doc Text:
To maintain optimal stability and performance of the GlusterFS client in Red Hat Enterprise Linux, this update applies a number of bug fixes to the glusterfs packages.
Clone Of:
Environment:
Last Closed: 2019-08-06 13:01:17 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2174 0 None None None 2019-08-06 13:01:18 UTC

Description Sunil Kumar Acharya 2018-12-07 08:26:12 UTC 
Description of problem:

Rebase glusterfs client rpms to the latest in RHEL 7.7

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 7 errata-xmlrpc 2019-08-06 13:01:17 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:2174
Note You need to log in before you can comment on or make changes to this bug.