Bug 1311362
Summary: | [AFR]: "volume heal info" command is failing during in-service upgrade to latest. | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Byreddy <bsrirama> | |
Component: | replicate | Assignee: | Anuradha <atalur> | |
Status: | CLOSED ERRATA | QA Contact: | Byreddy <bsrirama> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rhgs-3.1 | CC: | asrivast, atalur, byarlaga, nchilaka, pkarampu, rhinduja, rhs-bugs, smohan, storage-qa-internal | |
Target Milestone: | --- | Keywords: | ZStream | |
Target Release: | RHGS 3.1.3 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.7.9-4 | Doc Type: | Bug Fix | |
Doc Text: |
The heal info command expects bricks to have the .indices/dirty directory. However, older nodes do not have this directory. After in-service upgrades on a node, the heal info command failed when run from newer nodes due to missing .indices/dirty directory on old nodes. The missing directory is now ignored on older nodes and heal info command after in-service upgrades does not fail in this situation.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1332798 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-23 05:09:06 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: | 1268895, 1299184, 1332798, 1333239, 1333243 |
Description
Byreddy
2016-02-24 04:07:42 UTC
Verified this bug using the build - "glusterfs-3.7.9-4" Done the update from 3.1.1 to latest 3.1.3 build and found that "heal info" command is working good. Moving to verified state. Laura, I've made some changes. Please correct grammatical mistakes, if any. 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-2016:1240 |