more log false alarms

setup/so-verify

@@ -33,13 +33,17 @@ log_has_errors() {
     # Ignore Failed: 0 since that is the salt state output, and we detect state failures
     # via Result: False already.
 
-    # This is ignored for Ubuntu
+    # This is ignored for Ubuntu:
     # Failed to restart snapd.mounts-pre.target: Operation refused, unit snapd.mounts-pre.target
     # may be requested by dependency only (it is configured to refuse manual start/stop).
 
     # Command failed with exit code is output during retry loops.
 
     # "remove failed" is caused by a warning generated by upgrade of libwbclient
+
+    # Exit code 100 failure is likely apt-get running in the background, we wait for it to unlock.
+
+    # Failed to deduce dest mapping appears to occur when a shard isn't yet ready. Temporary.
     
     grep -E "FAILED|Failed|failed|ERROR|Result: False|Error is not recoverable" "$setup_log" | \
         grep -vE "The Salt Master has cached the public key for this node" | \
@@ -58,6 +62,7 @@ log_has_errors() {
         grep -vE "remove failed" | \
         grep -vE "Failed to restart snapd" | \
         grep -vE "Login Failed Details" | \
+        grep -vE "Failed to deduce dest mappings" | \
         grep -vE "response from daemon: unauthorized" | \
         grep -vE "Reading first line of patchfile" | \
         grep -vE "Command failed with exit code" | \