Reduce logspam of exception stacktraces for logs that can't be read

Logs not being able to be read is a common occurence when reading logs: a previous container often doesn't actually exist.
There is no easy way to detect this case without trying to read the logs

Author: vierbergenlars

contentgrid-junit-jupiter-k8s/src/main/java/com/contentgrid/junit/jupiter/k8s/wait/resource/PodAwaitableResource.java

@@ -50,7 +50,7 @@ private Stream<? extends LogLine> readContainer(PodResource resource, String con
                     .getLogReader()
             );
         } catch(KubernetesClientException exception) {
-            log.warn("Failed to read logs from {} container {}", this, containerName, exception);
+            logReadException(containerName, exception);
         }
 
         try {
@@ -62,11 +62,19 @@ private Stream<? extends LogLine> readContainer(PodResource resource, String con
                             .getLogReader()
             );
         } catch(KubernetesClientException exception) {
-            log.warn("Failed to read logs from {} container {}", this, containerName, exception);
+            logReadException(containerName, exception);
         }
         return logReaders.stream().flatMap(logReader -> readLogs(containerName, logReader));
     }
 
+    private void logReadException(String containerName, KubernetesClientException exception) {
+        if(log.isTraceEnabled()) {
+            log.warn("Failed to read logs from {} container {}", this, containerName, exception);
+        } else {
+            log.warn("Failed to read logs from {} container {}: {}", this, containerName, exception.getStatus().getMessage());
+        }
+    }
+
     private Stream<LogLine> readLogs(String containerName, Reader logReader) {
         return new BufferedReader(logReader).lines()
                 .map(line -> createLogLine(line, containerName));