k.rennerandClaude Opus 4.7
eefc0606e5
`kubectl logs -f --pod-running-timeout=10m` is unreliable as a wait barrier when the pod spends time in ContainerCreating (volume attach on RWX PVCs especially for the 300 GiB books PVC). It can return early without streaming, leaving the subsequent `kubectl wait --for=condition=complete --timeout=30s` to hit a Job that's still running and exit 1. Pipeline 750 (migrate-audiobookshelf) hit this: rsync started fine in the staging Job but the pipeline reported failure after 88 s — even though the Job kept running and the velero backup create that followed actually got submitted (Backup ended up in WaitingForPluginOperations). Replace the logs-and-wait dance with a 4 h-capped poll loop that reads the Job's Complete / Failed conditions directly. On Failed, print describe + last 100 log lines for diagnosis. On Complete, print the last 200 log lines for visibility. Same change applied to all 5 migrate-* pipelines. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>