Bug 1369723 - Update of glusterfs native client rpms in RHEL 7 rh-common channel
Summary: Update of glusterfs native client rpms in RHEL 7 rh-common channel
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: distribution
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: RHGS 3.1.3 Async
Assignee: Sreenath G
QA Contact: Anil Shah
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-24 08:44 UTC by Milind Changire
Modified: 2016-09-06 07:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, due to a bug in the libgfapi library, applications that used libgfapi to access Red Hat Gluster Storage sometimes became unresponsive or terminated with a segmentation fault. With this update, the issue in the glusterfs client packages have been fixed, and the applications can now access Red Hat Gluster Storage as expected. For more details, see also BZ# 1369390 and BZ# 1369412.
Clone Of:
Environment:
Last Closed: 2016-09-06 07:06:46 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1810 0 normal SHIPPED_LIVE Red Hat Gluster Storage 3.1 glusterfs Update 2016-09-06 11:04:33 UTC

Description Milind Changire 2016-08-24 08:44:17 UTC 
Async update is being provided with fixes for BZs:
https://bugzilla.redhat.com/1369390
https://bugzilla.redhat.com/1369412
Comment 3 Anil Shah 2016-09-02 12:10:49 UTC 
Installed/Updated RHEL 7 clients packages from rhel-7-server-rh-common channel
Comment 5 errata-xmlrpc 2016-09-06 07:06:46 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://rhn.redhat.com/errata/RHBA-2016-1810.html
Note You need to log in before you can comment on or make changes to this bug.