Bug 1079279

Summary:	glusterd: Log improvement needed for the message " E [glusterd-store.c:1957:glusterd_store_retrieve_volume] 0-: Unknown key: brick-0""
Product:	[Community] GlusterFS	Reporter:	Ravishankar N <ravishankar>
Component:	glusterd	Assignee:	Ravishankar N <ravishankar>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, gluster-bugs, nlevinki, ravishankar, spandura, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.6.0beta1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1056910	Environment:
Last Closed:	2014-11-11 08:29:06 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:	1056910
Bug Blocks:

Comment 1 Anand Avati 2014-03-21 11:29:41 UTC

REVIEW: http://review.gluster.org/7314 (glusterd: suppress spurious error message during startup) posted (#1) for review on master by Ravishankar N (ravishankar)

Comment 2 Anand Avati 2014-03-27 06:41:12 UTC

COMMIT: http://review.gluster.org/7314 committed in master by Anand Avati (avati) 
------
commit 468a14b8b10639f0983be57e985cc9db98c6550c
Author: Ravishankar N <ravishankar>
Date:   Mon Mar 10 06:55:11 2014 +0000

    glusterd: suppress spurious error message during startup
    
    From glusterd log:
    ----------
    E [glusterd-store.c:1981:glusterd_store_retrieve_volume] 0-: Unknown key:
    brick-0
    ----------
    
    The message is emitted from glusterd_store_retrieve_volume() when it reads the
    volinfo file because it doesn't do anything with the key-value pair. Suppress the
    error. The key is needed by glusterd_store_retrieve_bricks() which anyway
    re-reads it.
    
    Also change the log level to WARNING since we do not error out if an unknown key
    is got while parsing the volinfo file.
    
    Change-Id: Icd7962d9e16e0f90e6a37ee053dcafe97d2cab94
    BUG: 1079279
    Reviewed-on: http://review.gluster.org/7314
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Kaushal M <kaushal>
    Reviewed-by: Anand Avati <avati>

Comment 3 Niels de Vos 2014-09-22 12:37:08 UTC

A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED.

Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html
[2] http://supercolony.gluster.org/pipermail/gluster-users/

Comment 4 Niels de Vos 2014-11-11 08:29:06 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.6.1, please reopen this bug report.

glusterfs-3.6.1 has been announced [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html
[2] http://supercolony.gluster.org/mailman/listinfo/gluster-users