Skip to content
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

New scheduled backup gets triggered before last one completes #5989

Closed
navilg opened this issue Mar 16, 2023 · 2 comments
Closed

New scheduled backup gets triggered before last one completes #5989

navilg opened this issue Mar 16, 2023 · 2 comments
Assignees

Comments

@navilg
Copy link

navilg commented Mar 16, 2023

What steps did you take and what happened:

I have velero schedule which runs every 4 hours. Sometimes backup takes longer than 4 hours to complete. In that case new backup is triggered and that will be in NEW state and get piled up.

What did you expect to happen:

New scheduled backup should not be triggered unless last scheduled backup is completed from same schedule.

The following information will help us better understand what's going on:

If you are using velero v1.7.0+:
Please use velero debug --backup <backupname> --restore <restorename> to generate the support bundle, and attach to this issue, more options please refer to velero debug --help

If you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)

  • kubectl logs deployment/velero -n velero
  • velero backup describe <backupname> or kubectl get backup/<backupname> -n velero -o yaml
  • velero backup logs <backupname>
  • velero restore describe <restorename> or kubectl get restore/<restorename> -n velero -o yaml
  • velero restore logs <restorename>

Anything else you would like to add:

Environment:

  • Velero version (use velero version): 1.8.1
  • Velero features (use velero client config get features):
  • Kubernetes version (use kubectl version): 1.23
  • Kubernetes installer & version: GKE 1.23
  • Cloud provider or hardware configuration: GCP
  • OS (e.g. from /etc/os-release): Ubuntu

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"
@reasonerjt
Copy link
Contributor

@blackpiglet
I believe this has been fixed, please clarify.

@blackpiglet
Copy link
Contributor

@navilg
This issue is fixed by PR #5283. It's included in v1.10.x release.
Could you upgrade the Velero CRD and images, then have another try?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants