Velero 1.14.0 datamover cancels pods too early

[fgleixner]

What steps did you take and what happened:

Upgraded from 1.13.2 to 1.14.0. Backups completed with a lot of warnings:

message: /DataUpload is canceled, plugin: velero.io/csi-pvc-backupper

and the status of the dataupload says

message: 'found a dataupload velero/daily-backup-folio-prod-01-20240705194047-4dnqd
    with expose error: Pod is unschedulable: 0/15 nodes are available: pod has unbound
    immediate PersistentVolumeClaims. preemption: 0/15 nodes are available: 15 Preemption
    is not helpful for scheduling... mark it as cancel'

Some of the volumes work. Usually 4-5 volumes, all other fail.

What did you expect to happen:

Datauploader should wait some tome for the volumesnapshotcontents and the corresponding pvc to get ready like it was in velero 1.13.2

I use Longhorn as Storage provisioner.

Environment:

• Velero version (use velero version): 1.14.0
• Velero features (use velero client config get features): EnableCSI
• Kubernetes version (use kubectl version): 1.28.6
• Kubernetes installer & version: kubespray
• Cloud provider or hardware configuration: on premises
• OS (e.g. from /etc/os-release): SLES 15.5

Vote on this issue!

This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.

• 👍 for "I would like to see this bug fixed as soon as possible"
• 👎 for "There are more important bugs to focus on right now"

[Lyndon-Li]

Dup with #7898, the fix will be in 1.14.1

[reasonerjt]

Closing as a dup of #7898