Description of problem: ----------------------- Executing the 'gluster volume status' generates the warning message in glusterd.log. The warning message goes like this : <snip> "W [MSGID: 106217] [glusterd-op-sm.c:4706:glusterd_op_modify_op_ctx] 0-management: Failed uuid to hostname conversion" </snip> Version-Release number of selected component (if applicable): ------------------------------------------------------------- Layered installation - RHGS 3.2.0 (interim build - glusterfs-3.8.4-1.el7rhgs ) on RHEL 7.2 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Create any type of volume 2. Start the volume 3. Execute 'gluster volume status' Actual results: --------------- Warning message seen in the glusterd.log Expected results: ----------------- Clean pass of the 'gluster volume status' command Additional info: ---------------- The error snippet : <snip> [2016-09-22 09:21:38.536538] I [MSGID: 106499] [glusterd-handler.c:4360:__glusterd_handle_status_volume] 0-management: Received status volume req for volume test [2016-09-22 09:21:38.537509] W [MSGID: 106217] [glusterd-op-sm.c:4706:glusterd_op_modify_op_ctx] 0-management: Failed uuid to hostname conversion [2016-09-22 09:21:38.537533] W [MSGID: 106387] [glusterd-op-sm.c:4812:glusterd_op_modify_op_ctx] 0-management: op_ctx modification failed </snip>
upstream mainline patch http://review.gluster.org/#/c/15547 posted for review.
We are seeing this issue only during layered installation.
upstream mainline : http://review.gluster.org/15547 upstream 3.8 : http://review.gluster.org/15571 downstream patch : https://code.engineering.redhat.com/gerrit/85939 All the patches are merged now.
Verified this bug using the build 3.8.4-2. Fix is working good, not seeing the reported issue with the steps mentioned. Moving to verified state.
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-2017-0486.html