]> git.apps.os.sepia.ceph.com Git - ceph-ci.git/commit
qa/suites/upgrade/telemetry-upgrade: upgrade from reef instead of pacific
authorLaura Flores <lflores@ibm.com>
Tue, 11 Jun 2024 20:10:01 +0000 (15:10 -0500)
committerLaura Flores <lflores@ibm.com>
Tue, 11 Jun 2024 20:10:01 +0000 (15:10 -0500)
commit0b39555f9fcbb093ca03c7bad15acb4e368b99f0
tree260a22a708f6f1b86e2c4fd6d6b16a79bf0e2856
parentf2f7cc609cdbae767486cf2fe6872a4789adffb2
qa/suites/upgrade/telemetry-upgrade: upgrade from reef instead of pacific

With cephadm upgrades, we are only allowed to upgrade from as far back as N-2
releases. On the main branch, that means we can only upgrade from quincy and reef, and
we can no longer upgrade from pacific.

This test was trying to upgrade from pacific, which isn't allowed, which led to an
`UPGRADE_BAD_TARGET_VERSION` cluster error.

Fixes: https://tracker.ceph.com/issues/65189
Signed-off-by: Laura Flores <lflores@ibm.com>
12 files changed:
qa/suites/upgrade/telemetry-upgrade/pacific-x/% [deleted file]
qa/suites/upgrade/telemetry-upgrade/pacific-x/.qa [deleted symlink]
qa/suites/upgrade/telemetry-upgrade/pacific-x/0-random-distro$ [deleted symlink]
qa/suites/upgrade/telemetry-upgrade/pacific-x/0-start.yaml [deleted file]
qa/suites/upgrade/telemetry-upgrade/pacific-x/1-tasks.yaml [deleted file]
qa/suites/upgrade/telemetry-upgrade/reef-x/% [new file with mode: 0644]
qa/suites/upgrade/telemetry-upgrade/reef-x/.qa [new symlink]
qa/suites/upgrade/telemetry-upgrade/reef-x/0-random-distro$ [new symlink]
qa/suites/upgrade/telemetry-upgrade/reef-x/0-start.yaml [new file with mode: 0644]
qa/suites/upgrade/telemetry-upgrade/reef-x/1-tasks.yaml [new file with mode: 0644]
qa/workunits/test_telemetry_pacific.sh [deleted file]
qa/workunits/test_telemetry_pacific_x.sh [deleted file]