update master when putting metadata for CRR

When using the MongoDB backend, we have to pass
repairMaster to make it update the master with the
latest version, otherwise the master is only updated
when the version being put has the same versionId as
the master.

Issue: CLDSRV-618

Author: Kerkesni

lib/routes/routeBackbeat.js

@@ -619,6 +619,13 @@ function putMetadata(request, response, bucketInfo, objMd, log, callback) {
         // To prevent this, the versionId field is only included in options when it is defined.
         if (versionId !== undefined) {
             options.versionId = versionId;
+            // In the MongoDB metadata backend, setting the versionId option leads to the creation
+            // or update of the version object, the master object is only updated if its versionId
+            // is the same as the version. This can lead to inconsistencies when replicating objects
+            // in the wrong order (can happen when retrying after failures), where the master object
+            // might point to a non current version. To prevent this, we need to set repairMaster to
+            // true which will update the master to the latest version available at the time of the put.
+            options.repairMaster = true;
         }
 
         // If the new null keys logic (S3C-7352) is not supported (compatibility mode), 'isNull' remains undefined.