mirror of
https://github.com/vmware-tanzu/velero.git
synced 2026-09-13 03:24:39 +00:00
Chlins ZhangandGitHub
efc69c61aa
Run the E2E test on kind / setup-test-matrix (push) Failing after 4s
e2e-test-kind.yaml / extract (push) Failing after 7s
Run the E2E test on kind / get-go-version (push) Failing after 7s
Run the E2E test on kind / build (push) Skipped
Run the E2E test on kind / run-e2e-test (push) Skipped
push.yml / extract (push) Failing after 5s
Main CI / get-go-version (push) Failing after 6s
Main CI / Build (push) Skipped
Check the target PVC is not used by any active pod before any side effect, on both the CSI data mover path and the file system path. The in-use semantics align with the pvc-protection controller: terminal-phase pods don't block, terminating pods block with a wait hint. On the file system path, pods gated by this restore's restore-wait init container (identified by the restore UID in its args, and not yet terminated) are exempted: they must mount the PVC for the node-agent to restore the data and cannot write to the volume until the PodVolumeRestores complete. Leftover pods, controller-recreated pods, and pods gated by a different restore still block. Signed-off-by: chlins <chlins.zhang@gmail.com>