[Migrations] Upgrade tests to use 9.x compatible archives#193696

Merged

gsoldevila merged 5 commits intoelastic:mainfrom

gsoldevila:kbn-team-1113-upgrade-migration-tests-1

Sep 24, 2024

Member

gsoldevila commented Sep 23, 2024 •

edited by kibanamachine

Loading

Summary

Part of https://github.com/elastic/kibana-team/issues/1113

Merges some tested code paths into v2_migration.test.ts which uses an archive that is generated in 9.0.0.
Gets rid of the related failing tests.

gsoldevila added Team:Core release_note:skip Feature:Migrations backport:prev-major labels

gsoldevila force-pushed the kbn-team-1113-upgrade-migration-tests-1 branch from 568fd22 to a7e557a Compare

September 23, 2024 10:46

rudolf approved these changes

View reviewed changes

gsoldevila added 2 commits

September 23, 2024 15:24


          Merge some tests into v2_migration.test.ts

05e4d8c


          Merge more tests into v2_migration.test.ts

de60380

gsoldevila force-pushed the kbn-team-1113-upgrade-migration-tests-1 branch from a7e557a to de60380 Compare

September 23, 2024 13:24


          Merge corrupt_outdated_docs test in v2_migration.test.ts

bb9fe78

gsoldevila marked this pull request as ready for review

September 23, 2024 14:00

gsoldevila requested a review from a team as a code owner

September 23, 2024 14:00

Contributor

elasticmachine commented Sep 23, 2024

Pinging @elastic/kibana-core (Team:Core)

gsoldevila added 2 commits

September 23, 2024 18:26


          Fix the rest of the tests in group2

04f7bf8


          Fix outdated test

f5e6a13

gsoldevila enabled auto-merge (squash)

September 24, 2024 08:14

kibana-ci commented Sep 24, 2024

💛 Build succeeded, but was flaky

Buildkite Build
Commit: f5e6a13

Failed CI Steps

Metrics [docs]

✅ unchanged

History

💔 Build #236446 failed 04f7bf8
💔 Build #236387 failed bb9fe78

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

gsoldevila merged commit d4cc182 into elastic:main

kibanamachine added the v9.0.0 label

Contributor

kibanamachine commented Sep 24, 2024

💔 All backports failed

Status	Branch	Result
❌	8.15	Backport failed because of merge conflicts
❌	8.x	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 193696

Questions ?

Please refer to the Backport tool documentation

gsoldevila added backport:prev-minor and removed backport:prev-major labels

Contributor

kibanamachine commented Sep 25, 2024

💔 All backports failed

Status	Branch	Result
❌	8.x	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 193696

Questions ?

Please refer to the Backport tool documentation

This was referenced Sep 26, 2024

[8.x] [Migrations] Backport ALL updates to integration tests #194013

Merged

[Migrations] Fix integration tests that use ZIP archives that are not compatible with 9.0.0 #193856

Merged

Failing test: Jest Integration Tests.src/core/server/integration_tests/saved_objects/migrations/group6 - split .kibana index into multiple system indices failure cases when the .kibana migrator fails on the REINDEX_SOURCE_TO_TEMP_INDEX_BULK state is capable of successfully performing the split migration in subsequent restart #192719

Closed

Failing test: Jest Integration Tests.src/core/server/integration_tests/saved_objects/migrations/group6 - split .kibana index into multiple system indices failure cases when the .kibana_analytics migrator fails on the UPDATE_TARGET_MAPPINGS_PROPERTIES state is capable of successfully performing the split migration in subsequent restart #174311

Closed

Failing test: Jest Integration Tests.src/core/server/integration_tests/saved_objects/migrations/group6 - split .kibana index into multiple system indices failure cases when the .kibana_analytics migrator fails on the CLONE_TEMP_TO_TARGET state is capable of successfully performing the split migration in subsequent restart #174310

Closed

Failing test: Jest Integration Tests.src/core/server/integration_tests/saved_objects/migrations/group6 - split .kibana index into multiple system indices failure cases when the .kibana migrator fails on the CLONE_TEMP_TO_TARGET state is capable of successfully performing the split migration in subsequent restart #174308

Closed

Failing test: Jest Integration Tests.src/core/server/integration_tests/saved_objects/migrations/group2 - migration v2 migrates saved objects normally when multiple Kibana instances are started with an average interval #156117

Closed

kibanamachine added the backport missing label

gsoldevila mentioned this pull request

Saved object migrations using 7.x indices are not able to run against 9.0.0 #192633

Closed

Contributor

kibanamachine commented Oct 1, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

1 similar comment

Contributor

kibanamachine commented Oct 2, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add the label auto-backport or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 3, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

22 similar comments

Contributor

kibanamachine commented Oct 4, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 7, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 8, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 9, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 10, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 11, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 15, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 16, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 17, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 18, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 21, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 22, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 23, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 24, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 25, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 28, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 29, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 30, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Oct 31, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Nov 1, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Nov 4, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

Contributor

kibanamachine commented Nov 5, 2024

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 193696 locally

TinaHeiligers added the backport:skip label

kibanamachine removed the backport missing label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:skip Feature:Migrations release_note:skip Team:Core v9.0.0