+++ This bug was initially created as a clone of Bug #1643932 +++ Description of problem: gluster command on slave fails, geo-rep worker crashes with python3. Also geo-rep scheduler's Popen usage is not python3 compatible Version-Release number of selected component (if applicable): mainline How reproducible: Only on failure Steps to Reproduce: 1. 2. 3. Actual results: geo-rep crashes in python3 on failure. Expected results: geo-rep should not crash in python3 Additional info: --- Additional comment from Worker Ant on 2018-10-29 09:26:38 EDT --- REVIEW: https://review.gluster.org/21505 (georep: python2 to python3 compat - scheduler) posted (#2) for review on master by Kotresh HR --- Additional comment from Worker Ant on 2018-10-30 09:13:21 EDT --- REVIEW: https://review.gluster.org/21505 (georep: python2 to python3 compat - scheduler) posted (#3) for review on master by Amar Tumballi
REVIEW: https://review.gluster.org/21516 (georep: python2 to python3 compat - scheduler) posted (#1) for review on release-5 by Kotresh HR
REVIEW: https://review.gluster.org/21516 (georep: python2 to python3 compat - scheduler) posted (#2) for review on release-5 by Shyamsundar Ranganathan
Fixed in v5.1
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.1, please open a new bug report. glusterfs-5.1 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-November/000116.html [2] https://www.gluster.org/pipermail/gluster-users/