Skip to content

functionaltests: 7.x standalone -> 8.x standalone -> 9.x standalone -> 9.x managed #16199

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
ericywl opened this issue Mar 14, 2025 · 3 comments · Fixed by #16582
Closed

functionaltests: 7.x standalone -> 8.x standalone -> 9.x standalone -> 9.x managed #16199

ericywl opened this issue Mar 14, 2025 · 3 comments · Fixed by #16582
Assignees
@endorama @ericywl

Comments

@ericywl
Copy link
Contributor

ericywl commented Mar 14, 2025 •
edited
Loading

As per #16180, we need to reindex the data streams and indices before upgrading to 9.0+ version. The new steps would then be:

  1. Create 7.x standalone, ingest and check
  2. Upgrade to 8.x standalone, ingest and check
  3. Query deprecation warnings from ES, and perform reindexing / block writing to indices
  4. Upgrade to 9.x standalone, ingest and check
  5. Upgrade to 9.x managed, ingest and check
@ericywl ericywl changed the title 7.x standalone -> 8.x standalone -> 9.x standalone -> 9.x managed functionaltests: 7.x standalone -> 8.x standalone -> 9.x standalone -> 9.x managed Mar 14, 2025
@ericywl ericywl mentioned this issue Mar 14, 2025
Merged
@endorama
Copy link
Member

Q: is not clear to me why step 3 (Query deprecation warnings from ES, and perform reindexing / block writing to indices) only applies to standalone or it only applies to 9.1.0.

@endorama
Copy link
Member

Additional question: as we are reacting to ES migration deprecation logs, should we consider including this in our tests? For example if there are unaddressed deprecations, we may need to act on them either to make the test work or because they affect APM.

@ericywl
Copy link
Contributor Author

ericywl commented Mar 17, 2025

Q: is not clear to me why step 3 (Query deprecation warnings from ES, and perform reindexing / block writing to indices) only applies to standalone or it only applies to 9.1.0.

It applies to all 9.0+ versions I believe.

Additional question: as we are reacting to ES migration deprecation logs, should we consider including this in our tests? For example if there are unaddressed deprecations, we may need to act on them either to make the test work or because they affect APM.

Yes, I believe that's the intent. Maybe we can limit the ones we address to critical deprecation only.

@endorama endorama mentioned this issue Mar 17, 2025
Open
@ericywl ericywl mentioned this issue Mar 24, 2025
Closed
@ericywl ericywl mentioned this issue Apr 9, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@endorama endorama

@ericywl ericywl

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

functionaltests: Add test for 7x to 8x to 9x elastic/apm-server
2 participants
@endorama @ericywl