Bug 1122909

Summary: [BREW] incorrect package content description
Product: Red Hat Gluster Storage Reporter: Martin Kudlej <mkudlej>
Component: rhs-hadoopAssignee: Shubhendu Tripathi <shtripat>
Status: CLOSED ERRATA QA Contact: BigData QE <bigdata-qe-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.0CC: aavati, bchilds, eboyd, matt, nlevinki, rhs-bugs, sgraf, shtripat, swatt, vbellur
Target Milestone: Release CandidateKeywords: UpcomingRelease, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: rhs-hadoop-2.3.3-2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-24 11:55:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 1159155    

Description Martin Kudlej 2014-07-24 11:28:08 UTC
Description of problem:
Text from file HEADER from rpm package:

Description :
The Gluster Filesystem Hadoop implementation for both Hadoop 1.x and 2.x.  This
Java plugin for Hadoop allows MapReduce and YARN to run on top of Gluster, by providing the
GlusterFileSystem (1.x) and GlusterFs (2.x) implementations.  These should be referenced
in the hadoop configuration files and loaded at runtime as the FileSystem implementation.

I think this text should be corrected.

Version-Release number of selected component (if applicable):

Comment 3 Stanislav Graf 2014-11-18 12:54:24 UTC
This bug brought also this upstream commit:

This commit changes the name of a product.

Comment 4 Shubhendu Tripathi 2014-11-18 13:43:35 UTC
The product name was changed as per comments from Brad.
The product name should not be RedHat Storage as upstream it is known as GlusterFS.

Comment 5 errata-xmlrpc 2014-11-24 11:55:01 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.