Gluster users - Jul 2016 - Issue when upgrading from 3.6 to 3.7

When we upgrade some nodes from 3.6.1 to 3.7.13, some of the nodes give a
peer status of "peer rejected" while some dont. Is there a reason for
this
discrepency and will the steps mentioned in
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
work for this as well?

Just out of curiosity, why the line "Try the whole procedure a couple more
times if it doesn't work right away." in the link above?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160722/2074bf19/attachment.html>

Glusterd logs from all the nodes please?

On Friday 22 July 2016, B.K.Raghuram <bkrram at gmail.com> wrote:
> When we upgrade some nodes from 3.6.1 to 3.7.13, some of the nodes give a
> peer status of "peer rejected" while some dont. Is there a reason
for this
> discrepency and will the steps mentioned in
>
http://gluster-documentations.readthedocs.io/en/latest/Administrator%20Guide/Resolving%20Peer%20Rejected/
> work for this as well?
>
> Just out of curiosity, why the line "Try the whole procedure a couple
more
> times if it doesn't work right away." in the link above?
>

-- 
Atin
Sent from iPhone
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160722/c0c59d38/attachment.html>