Description of problem: The test case ./tests/bugs/replicate/bug-1433571-undo-pending-only-on-up-bricks.t is failing on some regression runs. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/20701 (cluster/afr: Fix bug-1433571-undo-pending-only-on-up-bricks.t) posted (#1) for review on master by Karthik U S
COMMIT: https://review.gluster.org/20701 committed in master by "Shyamsundar Ranganathan" <srangana> with a commit message- cluster/afr: Fix bug-1433571-undo-pending-only-on-up-bricks.t Problem: The test case was checking for the entry pending marker reset on the root after performing client side lookup at line #60-63. But sometimes the entry heal was not getting completed immediately. Fix: Wait for the entry heal to complete before checking the changelog. Change-Id: I42fde21b04a126ab044ce58373a996d72f125d96 fixes: bz#1614730 Signed-off-by: karthik-us <ksubrahm>
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.0, please open a new bug report. glusterfs-5.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/2018-October/000115.html [2] https://www.gluster.org/pipermail/gluster-users/