Red Hat Bugzilla – Bug 1231771
glusterd: Porting logging messages to new logging framework
Last modified: 2016-07-03 21:12:45 EDT
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Description of problem: The current implementation of logging is only available for some xlators. The logging have to be implemented for glusterd for better reading of log file and consistency. Version-Release number of selected component (if applicable): RHGS 3.1 How reproducible: N/A Steps to Reproduce: N/A Actual results: Unavailability of new logging mechanism (MSG ID) in glusterd. Expected results: Implement logging based on message ids for glusterd.
https://code.engineering.redhat.com/gerrit/#/c/50910 (backport of master: http://review.gluster.org/10473) is merged now.
https://code.engineering.redhat.com/gerrit/50888 (backport of master:http://review.gluster.org/9905) is merged now
Downstream - https://code.engineering.redhat.com/gerrit/50896 (backport of master:http://review.gluster.org/#/c/9952/) is merged now
This patch for the fix is not complete and few other patches[http://review.gluster.org/#/c/11388/1] needs to be merged. Marking this bug for the correct state
*** Bug 1235991 has been marked as a duplicate of this bug. ***
The last patch has been merged in downstream: https://code.engineering.redhat.com/gerrit/#/c/51682/ Upstream links: master: http://review.gluster.org/11388 release-3.7: http://review.gluster.org/11422
There are still 12 instances of gf_log instances seen in glusterd codebase. But these are introduced by Anuradha Talur with the patch - https://code.engineering.redhat.com/gerrit/#/c/51017/ The changes are minimal and doesn't impact much. Also all the patches mentioned in this bug ports most of gf_log to gf_msg messages Created a new bug - https://bugzilla.redhat.com/show_bug.cgi?id=1241649 for pending changes So marking this bug as VERIFIED for RHGS 3.1 release
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://rhn.redhat.com/errata/RHSA-2015-1495.html