fixup on verify replication error handling

Issue: S3UTILS-202

Author: SylvainSenechal

VerifyReplication/verifyReplication.js

@@ -43,15 +43,16 @@ function verifyObjects(objectList, cb) {
         return destinationStorage.getObjMd(params, (err, dstMd) => {
             ++statusObj.dstProcessedCount;
             if (err) {
-                ++statusObj.dstFailedMdRetrievalsCount;
-                logger.error('error getting metadata', {
-                    error: err,
-                    bucket: statusObj.dstBucket,
-                    key: dstKey,
-                    srcLastModified,
-                });
                 if (err instanceof NotFound) {
                     ++statusObj.missingInDstCount;
+                } else {
+                    ++statusObj.dstFailedMdRetrievalsCount;
+                    logger.error('error getting metadata', {
+                        error: err,
+                        bucket: statusObj.dstBucket,
+                        key: dstKey,
+                        srcLastModified,
+                    });
                 }
                 // log the error and continue processing objects
                 return done();

listFailedObjects.js

@@ -6,7 +6,6 @@ const http = require('http');
 const { Logger } = require('werelogs');
 
 const log = new Logger('s3utils:listFailedObjects');
-/* eslint-disable no-console */
 
 // configurable params
 const BUCKETS = process.argv[2] ? process.argv[2].split(',') : null;
@@ -129,4 +128,3 @@ async.mapSeries(
         }
     },
 );
-/* eslint-enable no-console */