Description of problem:
A geo-rep session was started between a 6 node master and slave cluster.
While running the scheduler script, it failed with the following:
[ OK] Stopped Geo-replication
[ OK] Set Checkpoint
[ OK] Started Geo-replication and watching Status for Checkpoint completion
Traceback (most recent call last):
File "/usr/share/glusterfs/scripts/schedule_georep.py", line 475, in <module>
File "/usr/share/glusterfs/scripts/schedule_georep.py", line 394, in main
File "/usr/share/glusterfs/scripts/schedule_georep.py", line 342, in get_summary
out.append([session_name, summary, faulty_rows, down_rows])
UnboundLocalError: local variable 'session_name' referenced before assignment
Version-Release number of selected component (if applicable):
The geo-rep scheduler script fails
The scheduler should not fail
REVIEW: https://review.gluster.org/19991 (geo-rep/scheduler: Fix crash) posted (#1) for review on master by Kotresh HR
COMMIT: https://review.gluster.org/19991 committed in master by "Kotresh HR" <email@example.com> with a commit message- geo-rep/scheduler: Fix crash
Fix crash where session_name is referenced
before assignment. Well, this is a corner
case where the geo-rep session exists and
the status output doesn't show any rows.
This might happen when glusterd is down
or when the system is in inconsistent state
Signed-off-by: Kotresh HR <firstname.lastname@example.org>
REVISION POSTED: https://review.gluster.org/20020 (geo-rep/scheduler: Fix crash) posted (#2) for review on release-3.12 by Kotresh HR
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.