Skip to content

Commit

Permalink
Updates archive again (elastic#209828)
Browse files Browse the repository at this point in the history
fix elastic#158318

Upgrading from `8.18.0` to `9.1.0` is not a supported upgrade path, nor
is upgrading from `8.19.0` to `9.0.0`.

These awkward upgrade paths have the unfortunate side effect that
migrations integration tests running against certain data archives fail
during backports, depending on the versions they're being backported
from and to.

This PR updates an archive to `8.19.0` in the hope that it will not
cause failures on backports from main to 9.0.0

---------

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Co-authored-by: Alejandro Fernández Haro <afharo@gmail.com>
  • Loading branch information
3 people authored Feb 11, 2025
1 parent c5557f3 commit 0b4d43e
Show file tree
Hide file tree
Showing 2 changed files with 1 addition and 2 deletions.
Binary file not shown.
Original file line number Diff line number Diff line change
Expand Up @@ -92,8 +92,7 @@ async function updateRoutingAllocations(
});
}

// FAILING ES PROMOTION: https://github.com/elastic/kibana/issues/158318
describe.skip('incompatible_cluster_routing_allocation', () => {
describe('incompatible_cluster_routing_allocation', () => {
let client: ElasticsearchClient;
let root: Root;

Expand Down

0 comments on commit 0b4d43e

Please sign in to comment.