[Bugs] [Bug 1238936] New: 'unable to get transaction op-info' error seen in glusterd log while executing gluster volume status command

[bugzilla at redhat.com]

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

            Bug ID: 1238936
           Summary: 'unable to get transaction op-info' error seen in
                    glusterd log while executing gluster volume status
                    command
           Product: GlusterFS
           Version: mainline
         Component: glusterd
          Keywords: Triaged
          Severity: medium
          Priority: low
          Assignee: bugs at gluster.org
          Reporter: amukherj at redhat.com
                CC: amukherj at redhat.com, bugs at gluster.org,
                    gluster-bugs at redhat.com, sasundar at redhat.com
        Depends On: 1233273



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

Description of problem:
-----------------------
While executing 'gluster volume status' command, the following error message
was seen,

<snip>
[2015-06-18 15:16:40.377993] E [glusterd-op-sm.c:251:glusterd_get_txn_opinfo]
(--> /usr/lib64/libglusterfs.so.0(_gf_log_callingfn+0x1e0)[0x7fc835252fc0] (-->
/usr/lib64/glusterfs/3.7.1/xlator/mgmt/glusterd.so(glusterd_get_txn_opinfo+0x197)[0x7fc829c80d67]
(-->
/usr/lib64/glusterfs/3.7.1/xlator/mgmt/glusterd.so(__glusterd_handle_stage_op+0x1f0)[0x7fc829c611a0]
(-->
/usr/lib64/glusterfs/3.7.1/xlator/mgmt/glusterd.so(glusterd_big_locked_handler+0x3f)[0x7fc829c5e53f]
(--> /usr/lib64/libglusterfs.so.0(synctask_wrap+0x12)[0x7fc8352935f2] )))))
0-management: Unable to get transaction opinfo for transaction ID :
c1d215cb-2b61-4ad4-828a-643f634a9e98
</snip>


Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHEL 6.7 Beta + glusterfs-3.7.1

How reproducible:
-----------------
Always

Steps to Reproduce:
--------------------
1. Create a volume of any type and start it
2. Execute 'gluster volume status' command
3. Check glusterd logs

Actual results:
---------------
Error messages as described earlier in the description was seen

Expected results:
-----------------
There shouldn't be any error messages

--- Additional comment from SATHEESARAN on 2015-06-18 11:04:48 EDT ---

I was managing gluster nodes in oVirt, which uses 'gluster volume status'
periodically to get the status/health of the gluster node

As a result, the error messages as indicated in comment0 gets filled all over
the glusterd logs.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1233273
[Bug 1233273] 'unable to get transaction op-info' error seen in glusterd
log while executing gluster volume status command
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.