Bug 1568251
Summary: | An error message 'invalid log level' is seen in heketi log during heketi startup | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | krishnaram Karthick <kramdoss> |
Component: | heketi | Assignee: | John Mulligan <jmulligan> |
Status: | CLOSED ERRATA | QA Contact: | Rachael <rgeorge> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | cns-3.9 | CC: | akrishna, hchiramm, jmulligan, pprakash, rhs-bugs, rtalur, sankarshan, storage-qa-internal, vinug |
Target Milestone: | --- | ||
Target Release: | CNS 3.10 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | heketi-6.0.0-14.el7rhgs | Doc Type: | Bug Fix |
Doc Text: |
Previously, Heketi configuration files that lacked a specific log level which caused the application to display a meaningless log message on startup. With this fix, Heketi ignores the lack of an explicit log level in the configuration file.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-09-12 09:22:12 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: | 1568861 |
Description
krishnaram Karthick
2018-04-17 04:02:06 UTC
We should fix this for 3.10. The heketi logs were searched for the error message mentioned in the bug, nos uch messages were found. [root@dhcp46-144 ~]# oc logs heketi-storage-1-56lwl |grep "invalid log level" [root@dhcp46-144 ~]# Verified on 2 different setups. Version-Release number of selected component: rhgs3/rhgs-volmanager-rhel7:3.3.1-15 Hence moving it to verified. Updated doc text in the Doc Text field. Please review for technical accuracy. Have updated the doc text based on the feed back given. (In reply to Anjana from comment #10) > Have updated the doc text based on the feed back given. Looks OK to me. 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:2686 |