velero backup status is ending in Partially Failed waiting for openstack snapshots to become available. #8140
-
What steps did you take and what happened: The following information will help us better understand what's going on: We are seeing an issue with Velero backups are Partially Failing because they are erroring out or timing out waiting for native velero snapshots that are created in openstack to become available. The environment we are hosting in openstack has some very large PVs (500Gb x 1 , 150Gb x 2 , 30G x 1 ) so it can take 10+ mins for the large snapshots that are created to become. The error message we are seeing in the backup details... Eventually the volume snapshots that are created by the velero backup in openstack are getting to an available state it is just taking a very long time. It has always taken a long time for the large snapshots to be created in openstack. It would appear that the maybe backup timeout settings are different for the with the latest version of velero ? current Kubernetes version 1.28.6 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.
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Are you using If so, that always works as you described because the |
Beta Was this translation helpful? Give feedback.
-
After using this as a reference the issue is now fixed Reference |
Beta Was this translation helpful? Give feedback.
After using this as a reference the issue is now fixed
openstack backups are now completing after increasing timeouts for
volumeTimeout: 5m
snapshotTimeout: 5m
cloneTimeout: 5m
backupTimeout: 5m
imageTimeout: 5m
Reference
https://github.com/Lirt/velero-plugin-for-openstack/blob/v0.7.0/docs/installation-using-helm.md