Bug 1815064 - Bring pyxattr with RHGS on RHEL8
Summary: Bring pyxattr with RHGS on RHEL8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: build
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: RHGS 3.5.z Batch Update 2
Assignee: Sreenath G
QA Contact: Vivek Das
URL:
Whiteboard:
Depends On:
Blocks: 1809957
TreeView+ depends on / blocked
 
Reported: 2020-03-19 11:59 UTC by Sunil Kumar Acharya
Modified: 2023-09-14 05:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-16 06:19:39 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:2572 0 None None None 2020-06-16 06:19:56 UTC

Description Sunil Kumar Acharya 2020-03-19 11:59:46 UTC 
Description of problem:

Creating placeholder bug to add pyxattr to RHEL8 channel for RHGS.

Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1809957#c2
Comment 2 Sreenath G 2020-03-27 10:10:24 UTC 
pyxattr-0.5.3-19.el8ost tagged to rhgs-3.5.1-rhel-8-candidate and now it can be attached to RHGS-3.5.z on RHEL-8
Comment 8 Vivek Das 2020-06-04 20:13:47 UTC 
Validated on stage, pyxattr is getting pulled from rhgs channel.

 python3-pyxattr     x86_64          0.5.3-19.el8ost      rh-gluster-3-for-rhel-8-x86_64-rpms   36 k


rpm -qa | grep pyxattr
python3-pyxattr-0.5.3-19.el8ost.x86_64

Marking the bug as verified.
Comment 10 errata-xmlrpc 2020-06-16 06:19: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/RHBA-2020:2572
Comment 12 Red Hat Bugzilla 2023-09-14 05:54:29 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.