Bug 1103623

Summary:	"volfile-max-fetch-attempts" was not deprecated correctly
Product:	[Community] GlusterFS	Reporter:	Poornima G <pgurusid>
Component:	logging	Assignee:	Poornima G <pgurusid>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	pre-release	CC:	bugs, fharshav, gluster-bugs, grajaiya, hchiramm, nlevinki, nsathyan, pgurusid, psriniva, sasundar, sdharane, vagarwal, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.6.0beta1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1061594	Environment:
Last Closed:	2014-11-11 08:33:50 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:	1045309, 1045313, 1061594
Bug Blocks:

Comment 1 Anand Avati 2014-06-02 08:51:28 UTC

REVIEW: http://review.gluster.org/7948 (logging: Prior to log initialization, print all logs to syslog.) posted (#1) for review on master by Poornima G (pgurusid)

Comment 2 Anand Avati 2014-06-06 05:12:45 UTC

COMMIT: http://review.gluster.org/7948 committed in master by Vijay Bellur (vbellur) 
------
commit 535003ca20a9dd00a09dd34ad26947d888aabe39
Author: Poornima G <pgurusid>
Date:   Mon Jun 2 14:11:29 2014 +0530

    logging: Prior to log initialization, print all logs to syslog.
    
    There can be calls to gf_msg even before caling logging_init().
    Currently such messages appear on stderr. In this patch, gf_msg
    is changed to log messages to syslog if the logging framework is
    not inited.
    
    Change-Id: I8fcf562f9d07b5b6b789fbd9e6f37b354de16b98
    BUG: 1103623
    Signed-off-by: Poornima G <pgurusid>
    Reviewed-on: http://review.gluster.org/7948
    Reviewed-by: Raghavendra Talur <rtalur>
    Reviewed-by: Atin Mukherjee <amukherj>
    Reviewed-by: Raghavendra G <rgowdapp>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Vijay Bellur <vbellur>

Comment 3 Niels de Vos 2014-09-22 12:41:36 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:33:50 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