Bug 1192452

Summary: After fresh install of gluster rpm's the log messages shows error for glusterd.info file as no such file or directory
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: surabhi <sbhaloth>
Component: glusterdAssignee: Bug Updates Notification Mailing List <rhs-bugs>
Status: CLOSED NOTABUG QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhgs-3.0CC: amukherj, nlevinki, pprakash, sasundar, sbhaloth, vagarwal, vbellur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: glusterd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1211718 (view as bug list) Environment:
Last Closed: 2016-01-07 08:49:58 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: 1211718    

Description surabhi 2015-02-13 11:49:43 UTC
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):
*******************************************
glusterfs-libs-3.6.0.44-1.el6rhs.x86_64
glusterfs-server-3.6.0.44-1.el6rhs.x86_64
samba-vfs-glusterfs-4.1.16-3.el6rhs.x86_64
glusterfs-api-3.6.0.44-1.el6rhs.x86_64
glusterfs-cli-3.6.0.44-1.el6rhs.x86_64
glusterfs-geo-replication-3.6.0.44-1.el6rhs.x86_64
glusterfs-3.6.0.44-1.el6rhs.x86_64
glusterfs-fuse-3.6.0.44-1.el6rhs.x86_64
glusterfs-rdma-3.6.0.44-1.el6rhs.x86_64


How reproducible:
*********************************************
Saw after fresh install.


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.


Additional info:

Comment 2 Prasanth 2015-02-16 05:42:57 UTC
Isn't this a duplicate of Bug 1110715?

Comment 3 surabhi 2015-02-16 11:40:22 UTC
I am not sure about the root cause but i see the error for glusterd.info file in gluster logs after fresh install, which should not happen.Discussed with KP and it needs to be fixed in gluster-server.I would like to track this seperately until the root cause is found for both the bz's.

Comment 4 SATHEESARAN 2015-04-14 17:18:12 UTC
(In reply to Prasanth from comment #2)
> Isn't this a duplicate of Bug 1110715?

Prasanth,

This is a different from BZ 1110715.

glusterd.info is generated lately, until a peer is probed or volume is created.
So what happens in the fresh installation is, glusterd finds this glusterd.info file is missing and reports it as an error in glusterd logs.

This bug is to move such an log message to INFO message, and not under ERROR category

Comment 5 Atin Mukherjee 2016-01-07 08:49:58 UTC
As this is expected as explained in #c4, closing this bug.