Bug 1691224 - [GSS]merge ctime upstream fix into the existing RHGS version
Summary: [GSS]merge ctime upstream fix into the existing RHGS version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: core
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: RHGS 3.5.0
Assignee: Kotresh HR
QA Contact: Nag Pavan Chilakam
URL:
Whiteboard:
Depends On: 1298724
Blocks: 1696806
TreeView+ depends on / blocked
 
Reported: 2019-03-21 08:00 UTC by amansan
Modified: 2019-10-31 12:37 UTC (History)
4 users (show)

Fixed In Version: glusterfs-6.0-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-30 12:20:22 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3249 0 None None None 2019-10-30 12:20:46 UTC

Description amansan 2019-03-21 08:00:29 UTC 
Description of problem:


Customer needs to have the fix of the bug into the existing RHGS version
Comment 5 Amar Tumballi 2019-03-25 14:00:11 UTC 
Alicia,

Please note that ctime feature is user invisible, intrusive change in the way gluster handles stat(man 2 stat) structure. Putting it in batch update would increase the risk of reducing the quality of the existing product. It also introduces a client side translator, and hence the Overall QE validation time after backport (which would take more time as we have done some coding standard related changes in upstream) would be more than RHGS 3.5 GA time. 

Please let the customer know that backport at present is not possible.
Comment 18 errata-xmlrpc 2019-10-30 12:20:22 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:3249
Note You need to log in before you can comment on or make changes to this bug.