[Bugs] [Bug 1394219] New: Better logging when reporting failures of the kind "< file-path> Failing MKNOD as quorum is not met"

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1394219

            Bug ID: 1394219
           Summary: Better logging when reporting failures of the kind
                    "<file-path> Failing MKNOD as quorum is not met"
           Product: Red Hat Gluster Storage
           Version: 3.2
         Component: replicate
          Keywords: Triaged
          Assignee: kdhananj at redhat.com
          Reporter: kdhananj at redhat.com
        QA Contact: nchilaka at redhat.com
                CC: bugs at gluster.org, rhs-bugs at redhat.com,
                    storage-qa-internal at redhat.com
        Depends On: 1392865
            Blocks: 1393629, 1393630, 1393631



+++ This bug was initially created as a clone of Bug #1392865 +++

Description of problem:

Often when debugging quorum failures, it helps to know the exact error code
because of which the fop is being failed.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Worker Ant on 2016-11-08 06:56:35 EST ---

REVIEW: http://review.gluster.org/15800 (cluster/afr: When failing fop due to
lack of quorum, also log error string) posted (#1) for review on master by
Krutika Dhananjay (kdhananj at redhat.com)

--- Additional comment from Worker Ant on 2016-11-09 05:27:50 EST ---

REVIEW: http://review.gluster.org/15800 (cluster/afr: When failing fop due to
lack of quorum, also log error string) posted (#2) for review on master by
Krutika Dhananjay (kdhananj at redhat.com)

--- Additional comment from Worker Ant on 2016-11-09 10:35:02 EST ---

REVIEW: http://review.gluster.org/15800 (cluster/afr: When failing fop due to
lack of quorum, also log error string) posted (#3) for review on master by
Krutika Dhananjay (kdhananj at redhat.com)

--- Additional comment from Worker Ant on 2016-11-09 19:45:19 EST ---

COMMIT: http://review.gluster.org/15800 committed in master by Pranith Kumar
Karampuri (pkarampu at redhat.com) 
------
commit f2e6cf9d9c578c58cdd348ebcd14dcbfdfbafadd
Author: Krutika Dhananjay <kdhananj at redhat.com>
Date:   Tue Nov 8 17:24:41 2016 +0530

    cluster/afr: When failing fop due to lack of quorum, also log error string

    Change-Id: I39de2bcfc660f23a4229a885a0e0420ca949ffc9
    BUG: 1392865
    Signed-off-by: Krutika Dhananjay <kdhananj at redhat.com>
    Reviewed-on: http://review.gluster.org/15800
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    Tested-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1392865
[Bug 1392865] Better logging when reporting failures of the kind
"<file-path> Failing MKNOD as quorum is not met"
https://bugzilla.redhat.com/show_bug.cgi?id=1393629
[Bug 1393629] Better logging when reporting failures of the kind
"<file-path> Failing MKNOD as quorum is not met"
https://bugzilla.redhat.com/show_bug.cgi?id=1393630
[Bug 1393630] Better logging when reporting failures of the kind
"<file-path> Failing MKNOD as quorum is not met"
https://bugzilla.redhat.com/show_bug.cgi?id=1393631
[Bug 1393631] Better logging when reporting failures of the kind
"<file-path> Failing MKNOD as quorum is not met"
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=A51NKWO8ex&a=cc_unsubscribe