+++ This bug was initially created as a clone of Bug #1506589 +++ Description of problem: After force start of the volume, brick port mismatch between volume status and ps output. Version-Release number of selected component (if applicable): RHGS 3.3 Actual results: Brick port is different in both volume status and ps output. Expected results: Brick port should be same in both volume status and ps output.
REVIEW: https://review.gluster.org/18589 (glusterd: persist brickinfo's port change into glusterd's store) posted (#1) for review on release-3.12 by Gaurav Yadav
COMMIT: https://review.gluster.org/18589 committed in release-3.12 by ------------- glusterd: persist brickinfo's port change into glusterd's store Problem: Consider a case where node reboot is performed and prior to reboot brick was listening to 49153. Post reboot glusterd assigned 49152 to brick and started the brick process but the new port was never persisted. Now when glusterd restarts glusterd always read the port from its persisted store i.e 49153 however pmap signin happens with the correct port i.e 49152. Fix: Make sure when glusterd_brick_start is called, glusterd_store_volinfo is eventually invoked. Change-Id: Ic0efbd48c51d39729ed951a42922d0e59f7115a1 BUG: 1507748 Signed-off-by: Gaurav Yadav <gyadav>
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-glusterfs-3.12.3, please open a new bug report. glusterfs-glusterfs-3.12.3 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] http://lists.gluster.org/pipermail/gluster-devel/2017-November/053983.html [2] https://www.gluster.org/pipermail/gluster-users/