[Backport 2025.1] Manager 3.5.0 release updates #10609
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
scylladbbot
force-pushed
the
backport/10586/to-2025.1
branch
2 times, most recently
from
986b2d3 to
fe57412
Compare
Since the Manager 3.5 is out, we need to cover an upgrade from 3.4.* versions now. Manager versions 3.4.1 and 3.4.2 are two versions used in Production in Cloud currently. (cherry picked from commit 43353af)
Scylla 2023.1 is not officially supported by the latest Manager release. Because of that, older enterprise jobs switched to run with 2024.1. All Debian jobs is set to run with 2024.2 to keep the coverage for this release after switching the majority of jobs to 2025.1. (cherry picked from commit c4927fb)
As the new minor release of Manager - 3.5.0 - is here, it is set to be a default one used in tests. Together with that, Scylla 2025.1 is added to manager_versions.yaml config and will be the default one to test with Manager 3.5.0. test_sdcm_mgmt_common.py tests have been updated accordingly. (cherry picked from commit 9940b54)
In previous implementation the test was trying to set rf=2 per each DC while one of DCs had only one node. As a result, the test failed with error (1) like "Datacenter us-west-2scylla_node_west doesn't have enough token-owning nodes for replication_factor=2" The new approach will dynamically define the number of nodes per DC and set this value to DC's replication factor. refs: 1. https://jenkins.scylladb.com/job/manager-3.5/job/ubuntu22-sanity-test/1/ (cherry picked from commit dd22413)
scylladbbot
force-pushed
the
backport/10586/to-2025.1
branch
from
fe57412 to
bccfaa3
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes scylladb/scylla-manager#4343
Manager tests, configuration files, CI updates to introduce new Manager version 3.5.0 into SCT.
Manager 3.5.0 is a default version used in tests
As the new minor release of Manager - 3.5.0 - is here, it is set to be a default one used in tests.
Together with that, Scylla 2025.1 is added to manager_versions.yaml config and will be the default one to test with Manager 3.5.0.
Changed Manager version to upgrade from to 3.4.*
Since the Manager 3.5 is out, we need to cover an upgrade from 3.4.* versions now.
Manager versions 3.4.1 and 3.4.2 are two versions used in Production in Cloud currently.
Covered Scylla 2024.1/2024.2 in some of the Manager jobs
Scylla 2023.1 is not officially supported by the latest Manager release. Because of that, older enterprise jobs switched to run with 2024.1. All Debian jobs is set to run with 2024.2 to keep the coverage for this release after switching the majority of jobs to 2025.1.
Get rf dynamically for repair test with multiDC cluster
In previous implementation the test was trying to set rf=2 per each DC while one of DCs had only one node.
As a result, the test failed with error like:
Datacenter us-west-2scylla_node_west doesn't have enough token-owning nodes for replication_factor=2The new approach will dynamically define the number of nodes per DC and set this value to DC's replication factor.
Testing
PR pre-checks (self review)
I added the relevant
backportlabelsI didn't leave commented-out/debugging code
(cherry picked from commit 43353af)
(cherry picked from commit c4927fb)
(cherry picked from commit 9940b54)
(cherry picked from commit dd22413)
Parent PR: #10586