-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DataUpload isn't canceled even the Backup is marked as "Failed" when Velero pod restarts #7230
Comments
It occurred at the moment during Velero deployment grace periods: the terminating velero server pod still doing the data upload flow while the new start velero server pod is marking the "Failed" status of DataUpload CR simultaneously. This corner case wouldn't happen If the velero pod is OOM killed, so we decided to postpone the repair for low priority. |
As @qiuming-best explained in this comment, this is not likely happen in real usage scenario. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands. |
unstale |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands. |
unstale |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. If a Velero team member has requested log or more information, please provide the output of the shared commands. |
unstale |
Have same issue, restart doesn't help it fails all the time with the same error
|
@rkashasl |
Hoever, when i completely removed velero from the cluster including all crds and then reconcile flux to get it back - all backups after provisioning have been completed successfully, but then i run command
|
I increased memory requests to 1Gi and limits to 2Gi, also adjust cpu requests to 250m and all started to work as it should |
Restart the Velero pod when the
Backup
CR is inInProgress
status (theDataUpload
CR is inAccept
status), theBackup
CR is marked asFailed
when the Velero pod starts up again, but theDataUpload
CR isn't canceled and after a while theBackup
CR is marked asWaitingForPluginOperations
thenCompleted
.And here is the final status of the backup with status as
Completed
but failureReason asfound a backup with status "InProgress" during the server starting, mark it as "Failed"
: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.
The text was updated successfully, but these errors were encountered: