podvolumebackup: data path backup failed: error getting snapshot id with error: error running command, stderr=Resolving password failed: Fatal: /tmp/credentials/velero/velero-repo-credentials-repository-password does not exist

[cszixin]

​Back up a deployment that has a hostPath PVC mounted on it. As a result, the corresponding PodVolumeBackup object reported an error. My node-agent YAML is as shown in the figure.​

PodVolumeBackup error

And there is a velero-repo-credentialsSecret in my system. Do the Velero and node-agent need to explicitly mount this Secret? If so, how do I mount it?​

[blackpiglet]

https://velero.io/docs/v1.17/file-system-backup/#limitations
Please refer to this document. The host path volume is not supported.

[cszixin]

Yes, I'm aware of this constraint. However, can we implement a mechanism to silently skip and exclude any hostPath PersistentVolumeClaims during backup, ensuring no failure status is reflected on the Backup CR?

[blackpiglet]

IMO, the current status of backups would be PartiallyFailed, if HostPath PVCs are included.
It correctly reflects the volume backup result, and the successfully backed-up volume data can still be used for restoration.

Could you give information about why that is not enough for your scenario?

[cszixin]

I found that this issue also frequently occurs with volumes that are not of the hostPath type, such as emptyDir volumes.

The scenario is as follows:

A pod contains two volumes - one is a PVC volume and the other is an emptyDir volume, each containing a file. When using Velero for backup, Velero creates two PodVolumeBackups. However, one PodVolumeBackup succeeds while the other fails. The failed one reports the error:

data path backup failed: error getting snapshot id with error: error running command, stderr=Resolving password failed: Fatal: /tmp/credentials/velero/velero-repo-credentials-repository-password does not exist