[Bugs] [Bug 1377097] New: The GlusterFS Callback RPC-calls always use RPC/XID 42

[bugzilla at redhat.com]

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

            Bug ID: 1377097
           Summary: The GlusterFS Callback RPC-calls always use RPC/XID 42
           Product: GlusterFS
           Version: mainline
         Component: rpc
          Keywords: Triaged
          Severity: medium
          Priority: medium
          Assignee: bugs at gluster.org
          Reporter: ndevos at redhat.com
                CC: bugs at gluster.org, rgowdapp at redhat.com,
                    skoduri at redhat.com



Created attachment 1202185
  --> https://bugzilla.redhat.com/attachment.cgi?id=1202185&action=edit
capture with NFS and Gluster traffice, showing the RPC/XID re-use

Description of problem:
The RPC/XID for callbacks has been hardcoded to GF_UNIVERSAL_ANSWER. In
Wireshark these RPC-calls are marked as "RPC retransmissions" because of
the repeating RPC/XID. This is most confusing when verifying the
callbacks that the upcall framework sends. There is no way to see the
difference between real retransmissions and new callbacks.


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

How reproducible:
100%

Steps to Reproduce:
1. enable features.cache-invalidation on a volume
2. start a capture of network traffic (tcpdump -iany -s0 -w/tmp/out.pcap tcp)
3. create and delete some files on the mountpoint
4. inspect the .pcap file with Wireskark and filter on 'glusterfs.cbk'
5. notice the "RPC retransmission of #..." on all callback packets

Actual results:
Wireshark thinks all callback packets are a retransmission. This is not the
case, the contents of the packets are different (except for the rpc.xid).

Expected results:
The rpc.xid should increase for each callback that gets sent (per client).

Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.