[Bugs] [Bug 1802041] Peer is already being detached from cluster.

[bugzilla at redhat.com]

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

Sanju <srakonde at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(akshayvijapur at gma
                   |                            |il.com)



--- Comment #3 from Sanju <srakonde at redhat.com> ---
Reading through the code, I don't see any bug.

We display this error message on peer detach if the op_ret or op_errno is
GD_FRIEND_STATE_BEFRIENDED, in set_probe_error_str():

      case GF_PROBE_FRIEND_DETACHING:
                snprintf(errstr, len,
                         "Peer is already being "
                         "detached from cluster.\n"
                         "Check peer status by running "
                         "gluster peer status");
                break;

Only in glusterd_deprobe_begin(), we set peerinfo->detaching to true.
        peerinfo->detaching = _gf_true;

In glusterd_deprobe_begin(), before setting peerinfo->detaching to true, if it
is already true, we set the op_errno to GD_FRIEND_STATE_BEFRIENDED, and hence
the error message.

   if (peerinfo->detaching) {
        ret = -1;
        if (op_errno)
            *op_errno = GF_DEPROBE_FRIEND_DETACHING;
        goto out;
    }

I believe there is no such bug exists in this code path.

You can look at the peer status output or get-state output before issuing the
peer detach command to check whether the peer is in the connected state. If you
find that the peer is in connected state but you still see the same error,
please get back to us with get-state output.

I would like to close the bug with resolution as NOTABUG. Please, let me know
what you think.

Thanks,
Sanju

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