Update git submodules

* Update plugins/replication from branch 'stable-3.1'
  to 17e8c41d5e7b83c419a52a6f7da0ad3ade514f76
  - Merge branch 'stable-3.0' into stable-3.1
    
    * stable-3.0:
      Call retryDone() when giving up after lock failures
      Fix issue with task cleanup after retry
    
    Change-Id: Id9ce63cd6112b3c8b16f9daafe3a8a982521baa9
    
  - Merge branch 'stable-2.16' into stable-3.0
    
    * stable-2.16:
      Call retryDone() when giving up after lock failures
      Fix issue with task cleanup after retry
    
    Change-Id: Id987043c8a26bd3f69fb4bd5b84591ae20cb83ba
    
  - Call retryDone() when giving up after lock failures
    
    Previously when giving up after retrying due to too many lock failures,
    a 'replication start --wait' command would wait indefinitely if it was
    waiting on the push that gave up. Fix this by calling retryDone() after
    giving up which will trigger the ReplicationStatus to reflect a failure
    allowing the waiting to complete.
    
    Change-Id: I0debade83612eb7ce51bab0191ab99464a6e7cd3
    
  - Fix issue with task cleanup after retry
    
    Destination.notifyFinished method calls finish on
    ReplicationTasksStorage.Task objects which are not scheduled for retry.
    
    The issue is that for rescheduled tasks PushOne.isRetrying
    will always returns true even if task is already replicated.
    That creates a situation where tasks scheduled for retry are
    never cleaned up.
    
    Bug: Issue 12754
    Change-Id: I4b10c2752da6aa7444f57c3ce4ab70eb00c3f14e
    

1 files changed, 0 insertions, 0 deletions

diff --git a/plugins/replication b/plugins/replication
-Subproject 2f29ef1c4c7c9893af0638ebc575cbd4b369118
+Subproject 17e8c41d5e7b83c419a52a6f7da0ad3ade514f7