K8sTaskHandler.savePodLogOnError warns a save log failure when fusion is enabled #6448
Description
Bug report
When using K8s with fusion enabled Nextflow is trying to save the pod log in the .command.log file that already exists because it has been created.
Expected behavior and actual behavior
It logs a warning "Failed to copy log for pod". It shouldn't log this warning
Steps to reproduce the problem
Run a pipeline with k8s and fusion where a task fails.
Program output
Sep-24 22:45:39.357 [Task monitor] WARN nextflow.k8s.K8sTaskHandler - Failed to copy log for pod nf-e715d5945772d1e3251b637a0dc5abdd-73362
java.nio.file.FileAlreadyExistsException: s3://xxxx/scratch/w9MbXcweUniun/e7/15d5945772d1e3251b637a0dbdd/.command.log
at nextflow.cloud.aws.nio.S3FileSystemProvider.newOutputStream(S3FileSystemProvider.java:261)
at java.base/java.nio.file.Files.newOutputStream(Files.java:228)
at java.base/java.nio.file.Files.copy(Files.java:3153)
at nextflow.k8s.K8sTaskHandler.savePodLogOnError(K8sTaskHandler.groovy:457)
at nextflow.k8s.K8sTaskHandler.checkIfCompleted(K8sTaskHandler.groovy:432)
at nextflow.processor.TaskPollingMonitor.checkTaskStatus(TaskPollingMonitor.groovy:659)
at nextflow.processor.TaskPollingMonitor.checkAllTasks(TaskPollingMonitor.groovy:578
Environment
- Nextflow version: 25.04.3
- Java version: 21
- Operating system: Linux
- Bash version: