Bug 1049481
| Summary: | Need better GlusterFS log message string when updating host definition | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Justin Clift <jclift> |
| Component: | cli | Assignee: | bugs <bugs> |
| Status: | CLOSED EOL | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.4.1 | CC: | bugs, gluster-bugs, kwade |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-10-07 12:31:36 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: | |||
GlusterFS 3.7.0 has been released (http://www.gluster.org/pipermail/gluster-users/2015-May/021901.html), and the Gluster project maintains N-2 supported releases. The last two releases before 3.7 are still maintained, at the moment these are 3.6 and 3.5. This bug has been filed against the 3,4 release, and will not get fixed in a 3.4 version any more. Please verify if newer versions are affected with the reported problem. If that is the case, update the bug with a note, and update the version if you can. In case updating the version is not possible, leave a comment in this bug report with the version you tested, and set the "Need additional information the selected bugs from" below the comment box to "bugs". If there is no response by the end of the month, this bug will get automatically closed. GlusterFS 3.4.x has reached end-of-life. If this bug still exists in a later release please reopen this and change the version or open a new bug. |
Description of problem: Recently, a GlusterFS SysAdmin was attempting to update host definitions in his GlusterFS cluster files, but was having trouble due to the uninformative log error message when he made a minor mistake. The log error messages he was seeing were: [2014-01-07 03:08:53.810098] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-0 [2014-01-07 03:08:53.810122] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-1 [2014-01-07 03:08:53.810132] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-2 [2014-01-07 03:08:53.810141] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-3 [2014-01-07 03:08:53.810149] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-4 [2014-01-07 03:08:53.810158] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-5 [2014-01-07 03:08:53.810167] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-6 [2014-01-07 03:08:53.810175] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-7 [2014-01-07 03:08:54.201857] E [glusterd-store.c:2487:glusterd_resolve_all_bricks] 0-glusterd: resolve brick failed in restore In this particular instance, he may have missed updating a host definition correctly on a host. To resolve the problem, the SysAdmin was able to revert his cluster configuration to the previous state (and will try again later). We could probably improve the log error message to be more informative, so problems like this are easier to diagnose and/or resolve. A suggested better error string from the SysAdmin is: [2014-01-07 xx:xx:xx.xxxxxx] E [glusterd-store.c:xxxx:glusterd_store_retrieve_volume] 0-: The brick filename specified in file "/path.../filename" does not exist in the brick directory "/path/..." This is likely an easy code change to make. :) Version-Release number of selected component (if applicable): 3.4.1 Additional info: http://supercolony.gluster.org/pipermail/gluster-users/2014-January/038501.html