Description of problem: brick process blindly takes the port that was allocated to it previously, and at the same time pmap allocates the same port to snapd. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/15001 (tests: Moving ./tests/bugs/snapshot/bug-1316437.t to bad test) posted (#1) for review on master by Avra Sengupta (asengupt)
COMMIT: http://review.gluster.org/15001 committed in master by Jeff Darcy (jdarcy) ------ commit 0d3e0da4fea3fa3acaab92a58d0b7c26bae765ff Author: Avra Sengupta <asengupt> Date: Mon Jul 25 16:23:06 2016 +0530 tests: Moving ./tests/bugs/snapshot/bug-1316437.t to bad test Moving ./tests/bugs/snapshot/bug-1316437.t to bad test, while mulling over the pros and cons of the fix. Will update the bug, as we go. Sending this patch to unblock master. Change-Id: Ia863312913686b4fa0ee0b63da13aedc0439a835 BUG: 1359717 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/15001 Smoke: Gluster Build System <jenkins.org> Reviewed-by: N Balachandran <nbalacha> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Jeff Darcy <jdarcy>
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-3.9.0, please open a new bug report. glusterfs-3.9.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] http://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html [2] https://www.gluster.org/pipermail/gluster-users/