Bug 1319670
Summary: | regression : RHGS 3.0 introduced a maximum value length in the info files | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Gaurav Kumar Garg <ggarg> |
Component: | glusterd | Assignee: | Satish Mohan <smohan> |
Status: | CLOSED ERRATA | QA Contact: | Byreddy <bsrirama> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.1 | CC: | amukherj, bkunal, bmohanra, bsrirama, byarlaga, cbuissar, rcyriac, rhinduja, rhs-bugs, sankarshan, sasundar, smohan, storage-qa-internal, vbellur |
Target Milestone: | --- | Keywords: | ZStream |
Target Release: | RHGS 3.1.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.7.9-1 | Doc Type: | Bug Fix |
Doc Text: |
Previously, if a user set an option where the number of characters in the key/value pair was greater than the value of PATH_MAX (4096), a restriction in the fgets operation meant that tokenizing the option failed. This meant that when users attempted to restart glusterd after setting a very long key/value pair, glusterd did not restart. This update ensures that the buffer length is controlled by the gf_store_read_and_tokenize operation so that tokenizing succeeds.
|
Story Points: | --- |
Clone Of: | 1269203 | Environment: | |
Last Closed: | 2016-06-23 05:04:46 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: | 1311817 |
Comment 3
Gaurav Kumar Garg
2016-03-21 10:10:32 UTC
downstream patch for this bug: https://code.engineering.redhat.com/gerrit/70324 Verified this bug using the build "glusterfs-3.7.9-1". Set a key/value longer than 4096 characters for a volume and restarted glusterd, restart worked properly without any error message. Steps done to verify: ===================== 1. Set the volume option "auth.allow" with 4109 characters 2. Restarted glusterd With these details, moving the bug to verified state LGTM :) 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 |