Description of problem: Since in container storage mode when gluster versions are changed as part of an upgrade workflow glusterd isn't brought up in interim upgrade mode which results in gluster brick processes to start with old brick volfiles which isn't functionally correct. Version-Release number of selected component (if applicable): mainline How reproducible: Always
REVIEW: https://review.gluster.org/21687 (glusterd: glusterd to regenerate volfiles on existence of glusterd.upgrade file) posted (#1) for review on master by Atin Mukherjee
REVIEW: https://review.gluster.org/21687 (glusterd: glusterd to regenerate volfiles when GD_OP_VERSION_MAX changes) posted (#6) for review on master by Amar Tumballi
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-6.0, please open a new bug report. glusterfs-6.0 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/000120.html [2] https://www.gluster.org/pipermail/gluster-users/