Skip to content

[CI] SystemIndicesUpgradeIT class failing #125623

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.

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

Closed
elasticsearchmachine opened this issue Mar 25, 2025 · 4 comments · Fixed by #127730
Closed

[CI] SystemIndicesUpgradeIT class failing #125623

elasticsearchmachine opened this issue Mar 25, 2025 · 4 comments · Fixed by #127730
Labels
:Core/Infra/Core Core issues without another label low-risk An open issue or test failure that is a low risk to future releases Team:Core/Infra Meta label for core/infra team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

Build Scans:

Reproduction Line:

undefined

Applicable branches:
8.x

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

undefined

Issue Reasons:

  • [8.x] 2 failures in class org.elasticsearch.upgrades.SystemIndicesUpgradeIT (0.2% fail rate in 1000 executions)
  • [8.x] 2 failures in step 8.0.1_bwc (100.0% fail rate in 2 executions)
  • [8.x] 2 failures in pipeline elasticsearch-periodic (66.7% fail rate in 3 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

@elasticsearchmachine elasticsearchmachine added :Core/Infra/Core Core issues without another label >test-failure Triaged test failures from CI Team:Core/Infra Meta label for core/infra team labels Mar 25, 2025
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-core-infra (Team:Core/Infra)

@elasticsearchmachine elasticsearchmachine added the needs:risk Requires assignment of a risk label (low, medium, blocker) label Mar 25, 2025
@ldematte
Copy link
Contributor

@alexey-ivanov-es do you thing this is solved by your latest changes?
It seems to be failing across multiple backward compatbility and upgrade tests.
Looking at the logs, I see

java.lang.AssertionError: expected empty context but was {X-elastic-product-origin=fleet}

@ldematte
Copy link
Contributor

It only happens with 8.0.1, but with 8.0.1 bwc it seems to be happening quite consistently (see also #125168)
Ah, it's a but on 8.0.1, we should probably just exclude this test too -- see #125167.

Since it's a test issue, I'll put low-risk, but probably we should fix it quick before it gets muted.

@ldematte ldematte added the low-risk An open issue or test failure that is a low risk to future releases label Mar 28, 2025
@elasticsearchmachine elasticsearchmachine removed the needs:risk Requires assignment of a risk label (low, medium, blocker) label Mar 28, 2025
@JVerwolf JVerwolf linked a pull request May 7, 2025 that will close this issue
@JVerwolf
Copy link
Contributor

JVerwolf commented May 7, 2025

Fixed by #127730

@JVerwolf JVerwolf closed this as completed May 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label low-risk An open issue or test failure that is a low risk to future releases Team:Core/Infra Meta label for core/infra team >test-failure Triaged test failures from CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants