qa/suites/thrash-old-clients/1-install: exclude ceph-osd-classic#66268
qa/suites/thrash-old-clients/1-install: exclude ceph-osd-classic#66268
Conversation
|
Taken from #66229, as this should fix thrash-old-clients tests |
28c1f68 to
412a0fc
Compare
ljflores
left a comment
There was a problem hiding this comment.
Changes look good to me. On the latest nightlies, the upgrade tests are also showing this error:
https://pulpito.ceph.com/teuthology-2025-11-16_20:00:21-rados-main-distro-default-smithi/8605314/
See https://pulpito.ceph.com/teuthology-2025-11-16_20:00:21-rados-main-distro-default-smithi/8605314/ for further examples.
So, we should also exclude the package for all releases in the upgrade suite that don't include it.
412a0fc to
12f520d
Compare
a37b5b5 added ceph-osd-classic package. old-clients and upgrade tests should not try to install the new package as it is not available in older releases. Fixes: https://tracker.ceph.com/issues/73848 Signed-off-by: Matan Breizman <mbreizma@redhat.com>
12f520d to
84d4206
Compare
Similarly to ceph#66268. Once crimson is enabled in RPM, ceph-osd-crimson will be requried as a dependency. old-clients and upgrade tests should not try to install the new package as it is not available in older releases. See: https://tracker.ceph.com/issues/73848 Signed-off-by: Matan Breizman <mbreizma@redhat.com>
Similarly to ceph#66268. Once crimson is enabled in RPM, ceph-osd-crimson will be requried as a dependency. old-clients and upgrade tests should not try to install the new package as it is not available in older releases. See: https://tracker.ceph.com/issues/73848 Signed-off-by: Matan Breizman <mbreizma@redhat.com>
|
The change here only impacts All upgrade and old-clients runs passed the package dependency installs successfully. |
|
This is an automated message by src/script/redmine-upkeep.py. I have resolved the following tracker ticket due to the merge of this PR: No backports are pending for the ticket. If this is incorrect, please update the tracker Update Log: https://github.com/ceph/ceph/actions/runs/19502384719 |
Similarly to ceph#66268. Once crimson is enabled in RPM, ceph-osd-crimson will be requried as a dependency. old-clients and upgrade tests should not try to install the new package as it is not available in older releases. See: https://tracker.ceph.com/issues/73848 Signed-off-by: Matan Breizman <mbreizma@redhat.com>
Similarly to ceph#66268. Once crimson is enabled in RPM, ceph-osd-crimson will be requried as a dependency. old-clients and upgrade tests should not try to install the new package as it is not available in older releases. See: https://tracker.ceph.com/issues/73848 Signed-off-by: Matan Breizman <mbreizma@redhat.com>
|
Thanks @Matan-B for the quick fix. |
Similarly to ceph#66268. Once crimson is enabled in RPM, ceph-osd-crimson will be requried as a dependency. old-clients and upgrade tests should not try to install the new package as it is not available in older releases. See: https://tracker.ceph.com/issues/73848 Signed-off-by: Matan Breizman <mbreizma@redhat.com>
Similarly to ceph#66268. Once crimson is enabled in RPM, ceph-osd-crimson will be requried as a dependency. old-clients and upgrade tests should not try to install the new package as it is not available in older releases. See: https://tracker.ceph.com/issues/73848 Signed-off-by: Matan Breizman <mbreizma@redhat.com>
Similarly to ceph#66268. Once crimson is enabled in RPM, ceph-osd-crimson will be requried as a dependency. old-clients and upgrade tests should not try to install the new package as it is not available in older releases. See: https://tracker.ceph.com/issues/73848 Signed-off-by: Matan Breizman <mbreizma@redhat.com>
Similarly to ceph#66268. Once crimson is enabled in RPM, ceph-osd-crimson will be requried as a dependency. old-clients and upgrade tests should not try to install the new package as it is not available in older releases. See: https://tracker.ceph.com/issues/73848 Signed-off-by: Matan Breizman <mbreizma@redhat.com>
Similarly to ceph#66268. Once crimson is enabled in RPM, ceph-osd-crimson will be requried as a dependency. old-clients and upgrade tests should not try to install the new package as it is not available in older releases. See: https://tracker.ceph.com/issues/73848 Signed-off-by: Matan Breizman <mbreizma@redhat.com>
a37b5b5 added ceph-osd-classic package. In old-clients tests we should try to install the new package as it is not available in older releases.
See for example the following thrash-old-clients:
https://pulpito.ceph.com/matan-2025-11-16_12:18:21-rados-wip-matanb-crimson-on-v2-distro-default-smithi/8605198
With the changes in this PR:
https://pulpito.ceph.com/matan-2025-11-16_12:58:48-rados-wip-matanb-crimson-on-v2-distro-default-smithi/
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.