diff options
author | Saravanakumar Arumugam <sarumuga@redhat.com> | 2016-06-29 15:36:06 +0530 |
---|---|---|
committer | Aravinda VK <avishwan@redhat.com> | 2016-08-19 03:46:52 -0700 |
commit | 10d044b62e476e032e8bda59fe8fbb3b8b0576b4 (patch) | |
tree | ea735960cae74441798f5f0684b07c7c213a393a /tests | |
parent | 56343cf608f02c2b6dbaef04ae7a897b13a97d42 (diff) |
glusterd/geo-rep: Handle empty monitor.status during upgrade
Problem:
Consider geo-replication is in Stopped state.
Following which, glusterfs is upgraded (where monitor.status is the
new status file).
Now, When geo-replication status command is run,
empty monitor status file gets created.
Now, if glusterd is restarted, it reads empty monitor status
and starts geo-replication session. This is incorrect as session
was in Stopped state earlier.
Solution:
If monitor status is empty, error out and avoid
starting geo-replication session.
Note: if monitor status is empty, geo-rep session is displayed
as Stopped state.
Change-Id: Ifb3db896e5ed92b927764cf1163503765cb08bb4
BUG: 1368053
Signed-off-by: Saravanakumar Arumugam <sarumuga@redhat.com>
> Reviewed-on: http://review.gluster.org/14830
> Smoke: Gluster Build System <jenkins@build.gluster.org>
> CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
> NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
> Reviewed-by: Jeff Darcy <jdarcy@redhat.com>
(cherry picked from commit f938b3a26ffab9482d5f910ee76d2bb2b370517f)
Reviewed-on: http://review.gluster.org/15196
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
Smoke: Gluster Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: Aravinda VK <avishwan@redhat.com>
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions