Bug 1501439
| Summary: | [GSS][Tracker] glusterfs plugin logs Warning|Info|Error messages even when --log-level=ERROR | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Nicolas Nosenzo <nnosenzo> |
| Component: | kubernetes | Assignee: | Humble Chirammal <hchiramm> |
| Status: | CLOSED ERRATA | QA Contact: | Neha Berry <nberry> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rhgs-3.0 | CC: | aivaraslaimikis, akrishna, amukherj, aos-bugs, aos-storage-staff, bkunal, dmoessne, eparis, hchiramm, jarrpa, jkaur, jmulligan, jolee, kramdoss, madam, rcyriac, rgeorge, rhs-bugs, rtalur, suchaudh |
| Target Milestone: | --- | ||
| Target Release: | CNS 3.10 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: |
Even though glusterfs fuse client log level has been set to ERROR, due to an issue in glusterfs client, it logs Info|Warn|Error messages regardless of the log level value set in the client process. This issue has been fixed with latest glusterfs client release.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-09-12 12:27:13 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: | 1544451 | ||
| Bug Blocks: | 1568861, 1573420 | ||
|
Description
Nicolas Nosenzo
2017-10-12 15:01:54 UTC
As an additional info there is also a KCS getting published to mitigate/workaround the issue we are seeing with this bug report. Should be fixed in the latest RHGS gluster client update. Updated the Doc Text field. kindly review Doc Text looks OK 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/RHEA-2018:2697 |