Skip to content
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

[CI] DiscoveryEc2AvailabilityZoneAttributeNoImdsIT testAvailabilityZoneAttribute failing #118564

Open
elasticsearchmachine opened this issue Dec 12, 2024 · 4 comments
Open

[CI] DiscoveryEc2AvailabilityZoneAttributeNoImdsIT testAvailabilityZoneAttribute failing #118564

elasticsearchmachine opened this issue Dec 12, 2024 · 4 comments
Assignees
@DaveCTurner
Labels
:Distributed Coordination/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure low-risk An open issue or test failure that is a low risk to future releases Team:Distributed Coordination Meta label for Distributed Coordination team >test-failure Triaged test failures from CI

Comments

@elasticsearchmachine
Copy link
Collaborator

elasticsearchmachine commented Dec 12, 2024 •
edited
Loading

Build Scans:

Reproduction Line:

./gradlew ":plugins:discovery-ec2:javaRestTest" --tests "org.elasticsearch.discovery.ec2.DiscoveryEc2AvailabilityZoneAttributeNoImdsIT.testAvailabilityZoneAttribute" -Dtests.seed=9867363BCF60CBE0 -Dtests.locale=fr-PF -Dtests.timezone=America/Knox_IN -Druntime.java=23

Applicable branches:
main

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

java.lang.AssertionError: expected null, but was:<us-west-2b>

Issue Reasons:

  • [main] 4 consecutive failures in step almalinux-8-aarch64_checkpart1_platform-support-arm
  • [main] 4 consecutive failures in step amazonlinux-2023_platform-support-aws
  • [main] 3 consecutive failures in step ubuntu-2004-aarch64_checkpart1_platform-support-arm
  • [main] 11 failures in test testAvailabilityZoneAttribute (7.2% fail rate in 152 executions)
  • [main] 4 failures in step almalinux-8-aarch64_checkpart1_platform-support-arm (100.0% fail rate in 4 executions)
  • [main] 4 failures in step amazonlinux-2023_platform-support-aws (100.0% fail rate in 4 executions)
  • [main] 3 failures in step ubuntu-2004-aarch64_checkpart1_platform-support-arm (100.0% fail rate in 3 executions)
  • [main] 4 failures in pipeline elasticsearch-periodic-platform-support (100.0% fail rate in 4 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
@elasticsearchmachine elasticsearchmachine added :Distributed Coordination/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure >test-failure Triaged test failures from CI needs:risk Requires assignment of a risk label (low, medium, blocker) Team:Distributed Coordination Meta label for Distributed Coordination team labels Dec 12, 2024
@elasticsearchmachine
Copy link
Collaborator Author

Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination)

@DaveCTurner DaveCTurner self-assigned this Dec 12, 2024
@DaveCTurner DaveCTurner added low-risk An open issue or test failure that is a low risk to future releases and removed needs:risk Requires assignment of a risk label (low, medium, blocker) labels Dec 12, 2024
DaveCTurner added a commit to DaveCTurner/elasticsearch that referenced this issue Dec 12, 2024
@DaveCTurner
Fix DiscoveryEc2AvailabilityZoneAttributeNoImdsIT
b0cf3d5 
This test asserts that no AZ attribute is set, assuming that the current
AZ is unavailable, but in fact that's not true when running these tests
in EC2. With this commit we override the IMDS endpoint address to one
that definitely does not exist.

Closes elastic#118564
@elasticsearchmachine
Copy link
Collaborator Author

This has been muted on branch 8.x

Mute Reasons:

  • [8.x] 3 consecutive failures in step part-1-arm
  • [8.x] 4 failures in test testAvailabilityZoneAttribute (16.0% fail rate in 25 executions)
  • [8.x] 3 failures in step part-1-arm (100.0% fail rate in 3 executions)
  • [8.x] 3 failures in pipeline elasticsearch-pull-request (30.0% fail rate in 10 executions)

Build Scans:

elasticsearchmachine added a commit that referenced this issue Dec 12, 2024
@elasticsearchmachine
Mute org.elasticsearch.discovery.ec2.DiscoveryEc2AvailabilityZoneAttr…
23ba880 
…ibuteNoImdsIT testAvailabilityZoneAttribute #118564
@mhl-b
Copy link
Contributor

mhl-b commented Dec 14, 2024

fixed here #118675

@mhl-b
Copy link
Contributor

mhl-b commented Dec 14, 2024

we can unmute 8.x after backport merged #118688

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

@DaveCTurner DaveCTurner

Labels
:Distributed Coordination/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure low-risk An open issue or test failure that is a low risk to future releases Team:Distributed Coordination Meta label for Distributed Coordination team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DaveCTurner @mhl-b @elasticsearchmachine