Bug 1211718

Summary: After fresh install of gluster rpm's the log messages shows error for glusterd.info file as no such file or directory
Product: [Community] GlusterFS Reporter: SATHEESARAN <sasundar>
Component: glusterdAssignee: Atin Mukherjee <amukherj>
Status: CLOSED WONTFIX QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: mainlineCC: amukherj, bugs, gluster-bugs, nlevinki, pprakash, rhs-bugs, sasundar, sbhaloth, vagarwal, vbellur
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: glusterd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1192452 Environment:
Last Closed: 2015-08-12 05:06:03 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: 1192452    
Bug Blocks:    

Description SATHEESARAN 2015-04-14 17:31:15 UTC
+++ This bug was initially created as a clone of Bug #1192452 +++

Description of problem:
*******************************************
After the fresh install of glusterfs the log file shows following error:

 E [store.c:432:gf_store_handle_retrieve] 0-: Path corresponding to /var/lib/glusterd/glusterd.info, returned error: (No such file or directory)
 E [store.c:432:gf_store_handle_retrieve] 0-: Path corresponding to /var/lib/glusterd/glusterd.info, returned error: (No such file or directory)
 E [store.c:432:gf_store_handle_retrieve] 0-: Path corresponding to /var/lib/glusterd/options, returned error: (No such file or directory)

Even though the info file gets created after glusterd service start we should not log this message as error after the fresh install.

Version-Release number of selected component (if applicable):
*******************************************
mainline


How reproducible:
*********************************************
Always


Steps to Reproduce:
1.Install latest glusterfs 
2.Verify the logs for any errors


Actual results:
********************************************
The log file shows errors for glusterd.info file as :
E [store.c:432:gf_store_handle_retrieve] 0-: Path corresponding to /var/lib/glusterd/glusterd.info, returned error: (No such file or directory)

Expected results:
***********************************************
It should not be logged as Error after the fresh install.

Comment 1 Atin Mukherjee 2015-08-12 05:06:03 UTC
The only way to get rid of this is to change the log level from ERROR to INFO as glusterd.info file gets created lately on the first probe or volume create. If we move the log level to INFO then the genuine errors can be ignored. I don't think we would need to fix this atm.