Bug 1771614

Summary: [RHEL 6] Installation of glusterfs-events package fails because of python dependency "python2-prettytable"
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Vivek Das <vdas>
Component: buildAssignee: Rinku <rkothiya>
Status: CLOSED ERRATA QA Contact: Vivek Das <vdas>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rhgs-3.5CC: pprakash, rcyriac, rhs-bugs, sgirijan, sheggodu, storage-qa-internal
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-6.0-22 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1773574 (view as bug list) Environment:
Last Closed: 2019-12-02 07:00:39 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: 1773574    

Description Vivek Das 2019-11-12 16:55:08 UTC
Description of problem:

yum install glusterfs-events fails for python2-prettytable.
Errata is complaining the same
python2-prettytable is needed by glusterfs-events-6.0-21.el6rhs.x86_64

Version-Release number of selected component (if applicable):
glusterfs-6.0-21.el6rhs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. yum install glusterfs-events package
2.
3.

Actual results:
Installation fails

Expected results:
Installation should succeed

Additional info:

Comment 7 Vivek Das 2019-11-15 09:07:20 UTC
The issue is now resolved with the fix available in "glusterfs-6.0-22.el6rhs.x86_64"

Sunil, can you please put the fixed-in version

Comment 8 Vivek Das 2019-11-15 12:18:49 UTC
Fixed In Version is now in place. Moving the bug to verified.

Comment 9 Sreenath G 2019-11-15 14:18:08 UTC
*** Bug 1732343 has been marked as a duplicate of this bug. ***

Comment 11 errata-xmlrpc 2019-12-02 07:00:39 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/RHEA-2019:4022