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

test(manager): introduce Manager installation test on different OS (backport #7456) #7584

Merged
merged 1 commit into from
Jun 6, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Jun 6, 2024

Closes scylladb/scylla-manager#3852

The test is designed for execution on non-main OS distributions (for example, debian10) where the main goal is to execute installation test and verify manager + agent are up and running.

The motivation of having such a test:

  • We have never faced OS-specific failures in backup/restore/repair functionality. Thus, there is no need to run the sanity test (which includes these functionality verification) against non-main operation systems;
  • Installation test takes only 20 minutes in average against ~2 hours for Manager sanity test;
  • The Manager sanity is still here and will be executed on the main OS - Ubuntu 22.

Testing

PR pre-checks (self review)

  • I added the relevant backport labels
  • I didn't leave commented-out/debugging code

Reminders

  • Add New configuration option and document them (in sdcm/sct_config.py)
  • Add unit tests to cover my changes (under unit-test/ folder)
  • Update the Readme/doc folder relevant to this change (if needed)

This is an automatic backport of pull request #7456 done by [Mergify](https://mergify.com).

The test is intended for execution on non-main OS distributions (for
example, debian10) where the main goal is to execute installation test
and verify manager + agent are up and running.

(cherry picked from commit 1293b0a)
@vponomaryov vponomaryov merged commit 97ca7db into manager-3.2 Jun 6, 2024
5 of 7 checks passed
@mergify mergify bot deleted the mergify/bp/manager-3.2/pr-7456 branch June 6, 2024 11:29
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

Successfully merging this pull request may close these issues.

2 participants