Created attachment 1539843 [details] logs on srv1 after upgrading and starting glusterfs Description of problem: Online upgrade for replicated volumes cause upgraded node to be in "Peer Rejected" state. Version-Release number of selected component (if applicable): From 4.1.7 to 5.4 How reproducible: Always Steps to Reproduce: 1. setup replicated volume on v4.1 2. kill all gluster* processes on the first node 3. upgrade rpms up to v5.4 4. start gluster* processes on the first node Actual results: Peer is being rejected. And cluster operates without upgraded node. `gluster peer status` shows: State: Peer Rejected (Connected) Expected results: Online upgrade should works without downtime Additional info: Please see logs file in the attachment.
Created attachment 1539845 [details] logs on srv2 after upgrading srv1
upstream patch: https://review.gluster.org/#/c/glusterfs/+/22297/
REVIEW: https://review.gluster.org/22314 (core: make compute_cksum function op_version compatible) posted (#1) for review on release-5 by Sanju Rakonde
REVIEW: https://review.gluster.org/22314 (core: make compute_cksum function op_version compatible) merged (#5) on release-5 by Shyamsundar Ranganathan
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.5, please open a new bug report. glusterfs-5.5 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2019-March/000119.html [2] https://www.gluster.org/pipermail/gluster-users/