Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1426559 - heal info is not giving correct output
heal info is not giving correct output
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: disperse (Show other bugs)
3.2
Unspecified Unspecified
unspecified Severity high
: ---
: RHGS 3.2.0
Assigned To: Pranith Kumar K
nchilaka
: Regression
Depends On: 1414287 1415082
Blocks: 1351528
  Show dependency treegraph
 
Reported: 2017-02-24 05:00 EST by Pranith Kumar K
Modified: 2017-03-23 02:05 EDT (History)
12 users (show)

See Also:
Fixed In Version: glusterfs-3.8.4-16
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1406322
Environment:
Last Closed: 2017-03-23 02:05:48 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:0486 normal SHIPPED_LIVE Moderate: Red Hat Gluster Storage 3.2.0 security, bug fix, and enhancement update 2017-03-23 05:18:45 EDT

  None (edit)
Comment 3 Atin Mukherjee 2017-02-24 05:21:18 EST
upstream patch : https://review.gluster.org/#/c/16468/
Comment 6 nchilaka 2017-03-08 03:47:19 EST
QATP: build 3.8.4-17:
1) ran continuous IO to a file, not seeing the entry of the file in heal info anymore(previously we used to see in heal info even though no heal was required) ==>pass
2)Ran kernel untar when all bricks up, and heal info didnt show any spurious entry of the file being untarred ==>pass
3)turned off selfhealdeamon: named lookups will only heal the name and should not heal any of the entry or data or metadata healing -->pass


hence moving to verified
Comment 8 errata-xmlrpc 2017-03-23 02:05:48 EDT
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/RHSA-2017-0486.html

Note You need to log in before you can comment on or make changes to this bug.