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

Extend Scylla Manager E2E with backup and manual restore procedure #1671

Closed
Tracked by #1897
rzetelskik opened this issue Jan 3, 2024 · 0 comments · Fixed by #1742
Closed
Tracked by #1897

Extend Scylla Manager E2E with backup and manual restore procedure #1671

rzetelskik opened this issue Jan 3, 2024 · 0 comments · Fixed by #1742
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@rzetelskik
Copy link
Member

What should the feature do?

Until recently, we weren't testing the automated backup procedure due to lack of access to object storage. We should extend the existing E2E test for Scylla Manager with an actual backup to object storage and a manual restore procedure.

What is the use case behind this feature?

Verifying correctness of automated backup and manual restore procedure using Scylla Manager.

Anything else we need to know?

No response

@rzetelskik rzetelskik added kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Jan 3, 2024
@tnozicka tnozicka added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Jan 4, 2024
@scylla-operator-bot scylla-operator-bot bot removed the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Jan 4, 2024
@tnozicka tnozicka added triage/accepted Indicates an issue or PR is ready to be actively worked on. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Jan 4, 2024
@tnozicka tnozicka removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants