Description of problem: The following error message is seen in heketi log when heketi is started. [heketi] ERROR 2018/04/16 14:34:34 /src/github.com/heketi/heketi/apps/glusterfs/app.go:100: invalid log level: heketi log: Heketi 6.0.0 [heketi] INFO 2018/04/16 14:34:34 Loaded kubernetes executor [heketi] ERROR 2018/04/16 14:34:34 /src/github.com/heketi/heketi/apps/glusterfs/app.go:100: invalid log level: [heketi] INFO 2018/04/16 14:34:34 Block: Auto Create Block Hosting Volume set to true [heketi] INFO 2018/04/16 14:34:34 Block: New Block Hosting Volume size 100 GB [heketi] INFO 2018/04/16 14:34:34 GlusterFS Application Loaded [heketi] INFO 2018/04/16 14:34:34 Started Node Health Cache Monitor Listening on port 8080 I'm not sure if this error message is significant, I can see all the usual logs being logged in heketi Version-Release number of selected component (if applicable): rhgs-volmanager-container-3.3.1-8.4 How reproducible: always Steps to Reproduce: 1. create a heketi container and check heketi logs Actual results: An error message on log level is seen Expected results: if the message doesn't make any significance, this error should be logged Additional info:
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