autobuild: intermittent test failure detected

[autobuild]

The autobuild test system has detected an intermittent failing test in 
the current master tree.

The autobuild log of the failure is available here:

   http://git.samba.org/autobuild.flakey/2013-12-17-1421/flakey.log

The samba3 build logs are available here:

   http://git.samba.org/autobuild.flakey/2013-12-17-1421/samba3.stderr
   http://git.samba.org/autobuild.flakey/2013-12-17-1421/samba3.stdout

The source4 build logs are available here:

   http://git.samba.org/autobuild.flakey/2013-12-17-1421/samba.stderr
   http://git.samba.org/autobuild.flakey/2013-12-17-1421/samba.stdout
  
The top commit at the time of the failure was:

commit fdccaab2a9a1b9d7eebcd7a4d121dbf68ea48dcd
Author: Martin Schwenke <martin at meltin.net>
Date:   Mon Dec 9 15:54:52 2013 +1100

    ctdb/eventscripts: Do not reconfigure in "monitor" events
    
    "monitor" events can be cancelled.  If a reconfigure action does a
    service restart then the "monitor" event can be cancelled at the
    inconvenient moment after the service is stopped.  In this case the
    service stays down and the node may become unhealthy (depending on
    whether there are any repair actions in the monitor event).
    
    A long time ago we did service reconfiguration in "monitor" events
    following failovers.  Service reconfiguration was then moved to the
    "ipreallocated" event.  However, reconfiguration in "monitor" events
    has been kept as a last resort in case an "ipreallocate" event does
    not occur.  The only important case that this covers is "ctdb
    deleteip", where "releaseip" events are generated without a
    corresponding "ipreallocated".  Therefore, IPs can be deleted without
    running the required service reconfiguration.
    
    The supported way of removing IP addresses is now via "ctdb
    reloadips", which always causes a takeover run with a corresponding
    "ipreallocate" event.
    
    This means that service reconfiguration in "monitor" events is no
    longer required and should be removed because it is unsafe.
    
    Also update the associated tests.  Make the first confirm that the
    monitor event no longer does reconfiguration.  Change the others to
    test that monitor status is correctly replayed when something else is
    doing a reconfigure and currently holds the reconfigure lock.
    
    Signed-off-by: Martin Schwenke <martin at meltin.net>
    Reviewed-by: Amitay Isaacs <amitay at gmail.com>
    
    Autobuild-User(master): Amitay Isaacs <amitay at samba.org>
    Autobuild-Date(master): Tue Dec 17 06:32:35 CET 2013 on sn-devel-104