qa/suites/upgrade: update upgrade paths and exclude rocky10 from non-supported distros#67127
Open
qa/suites/upgrade: update upgrade paths and exclude rocky10 from non-supported distros#67127
Conversation
a2879f4 to
f52f585
Compare
|
This pull request can no longer be automatically merged: a rebase is needed and changes have to be manually resolved |
f52f585 to
af8353e
Compare
|
This pull request can no longer be automatically merged: a rebase is needed and changes have to be manually resolved |
af8353e to
4c7e4c5
Compare
batrick
added a commit
to batrick/ceph
that referenced
this pull request
Feb 12, 2026
* refs/pull/67127/head: qa/suites/upgrade: exclude rocky when Squid is involved qa/suites/upgrade: update upgrade paths
14 tasks
Reef is EOL, so it should be removed from the upgrade paths. Upgrade paths only go as far back as two releases, and since the last two releases are Tentacle and Squid, Reef is outside of this "N-2" schema. Since Squid and Tentacle are the latest stable releases if we look back from "main", then we need to make sure to add Tentacle to the upgrade paths. This modification is prompted by the fact that we can't test upgrade paths from Reef to Main on Rocky10 packages. But this change should happen regardless. Fixes: https://tracker.ceph.com/issues/74609 Signed-off-by: Laura Flores <lflores@ibm.com>
2bf5f5e to
3578cb1
Compare
Rocky10 is not supported for Squid. Under the "squid-x" tests, I made a new folder that contains all the supported distros except for rocky10. Fixes: https://tracker.ceph.com/issues/74609 Signed-off-by: Laura Flores <lflores@ibm.com>
3578cb1 to
07ef68f
Compare
Member
Author
|
(just fixed the |
NitzanMordhai
approved these changes
Feb 26, 2026
Member
|
This PR is under test in https://tracker.ceph.com/issues/75377. |
14 tasks
Contributor
|
Why are some files renamed while some are deleted then recreated? e.g., |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Reef is EOL, so it should be removed from the upgrade paths. Upgrade paths only go as far back as two releases, and since the last two releases are Tentacle and Squid, Reef is outside of this "N-2" schema.
Since Squid and Tentacle are the latest stable releases if we look back from "main", then we need to make sure to add Tentacle to the upgrade paths.
This modification is prompted by the fact that we can't test upgrade paths from Reef to Main on Rocky10 packages. But this change should happen regardless.
Fixes: https://tracker.ceph.com/issues/74609
These changes are already being handled as a part of #66524, but I wanted to create a separate PR (marked Draft for now) so we can test this along with the rest of the Rocky10 work.
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins test classic perfJenkins Job | Jenkins Job Definitionjenkins test crimson perfJenkins Job | Jenkins Job Definitionjenkins test signedJenkins Job | Jenkins Job Definitionjenkins test make checkJenkins Job | Jenkins Job Definitionjenkins test make check arm64Jenkins Job | Jenkins Job Definitionjenkins test submodulesJenkins Job | Jenkins Job Definitionjenkins test dashboardJenkins Job | Jenkins Job Definitionjenkins test dashboard cephadmJenkins Job | Jenkins Job Definitionjenkins test apiJenkins Job | Jenkins Job Definitionjenkins test docsReadTheDocs | Github Workflow Definitionjenkins test ceph-volume allJenkins Jobs | Jenkins Jobs Definitionjenkins test windowsJenkins Job | Jenkins Job Definitionjenkins test rook e2eJenkins Job | Jenkins Job DefinitionYou must only issue one Jenkins command per-comment. Jenkins does not understand
comments with more than one command.