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

Scheduler should not create Backups until outstanding backups for the schedule have completed #3554

Closed
dsu-igeek opened this issue Mar 10, 2021 · 4 comments

Comments

@dsu-igeek
Copy link
Contributor

What steps did you take and what happened:
If a scheduled backup time is reached while a previous backup for the schedule is running, a new Backup resource is created. This can result in multiple Backups being queued that will all get executed together when the queue is unstalled.

What did you expect to happen:
Backups should not be queued until any previous backups for the schedule have completed.

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

stale bot commented Nov 14, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the staled label Nov 14, 2021
@stale
Copy link

stale bot commented Nov 29, 2021

Closing the stale issue.

@stale stale bot closed this as completed Nov 29, 2021
@reasonerjt
Copy link
Contributor

Not a stale reopening.

@reasonerjt reasonerjt reopened this Dec 21, 2021
@stale stale bot removed the staled label Dec 21, 2021
@blackpiglet
Copy link
Contributor

This issue is already fixed by PR #5283

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

No branches or pull requests

4 participants