syncdaemon: fix setting None as new master

We checked for the event of a new master being adopted by:
- checking for state change in list of masters
- checking if our chosen master is a foreign one
and if these held, then wrote out the actually available master to config

However this was flaky: if
(1) native master changed
(2) there was already a foreign master adopted
(3) actually the master was not available
then we wrote out the None to config.

This could occur if:
- on syncd startup, native master just changes from None to the volume native
  [implies (1)]
- foreign master adopted from earlier run via config [implies (2)]
- actually foreign master was not available [implies (3)]

Signed-off-by: Csaba Henk <csaba@gluster.com>
Signed-off-by: Anand Avati <avati@gluster.com>

BUG: 2670 (strange behaviour with intermediate-master and slave)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2670

0 files changed, 0 insertions, 0 deletions