Bug 1306877
| Summary: | volume reset of log levels does not return them to the default | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Joe Julian <joe> |
| Component: | glusterd | Assignee: | bugs <bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.6.8 | CC: | amukherj, bugs, hgowtham, joe, kaushal, smohan |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | Flags: | amukherj:
needinfo?
|
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-01 04:42:38 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: | 1308902 | ||
| Bug Blocks: | |||
This is fixed in latest releases (3.7 & 3.8) of GlusterFS with http://review.gluster.org/#/c/11887 , given that 3.6 will be EOLed once 3.9 is out (in another 3 months) do you see a strong reason to backport it to 3.6 branch? This is not a security bug, not going to fix this in 3.6.x because of http://www.gluster.org/pipermail/gluster-users/2016-July/027682.html If the issue persists in the latest releases, please feel free to clone them |
If you change the log level gluster volume set myvol diagnostics.brick-log-level DEBUG then reset the log level gluster volume reset myvol diagnostics.brick-log-level the process will continue to log at the DEBUG level instead of returning to INFO despite resetting the value in glusterd's view of the graph - removing it from gluster volume info.