[9.2] (backport #10943) fix: pass all necessary env vars so retried fips steps provision ESS #10951
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
mergify bot requested review from pkoutsovasilis and swiatekm and removed request for a team 
github-actions bot added Team:Elastic-Agent-Control-Plane 
| Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
pkoutsovasilis previously approved these changes Oct 31, 2025
pkoutsovasilis dismissed their stale review the staging FIPS-complaint cloud env isn't enabled here
ebeahan approved these changes Oct 31, 2025
swiatekm approved these changes Oct 31, 2025
💛 Build succeeded, but was flaky
Failed CI Steps |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR adds the required environment variables (
EC_ENDPOINTandESS_REGION) to all FIPS integration test steps in the Buildkite pipeline to ensure proper ESS (Elastic Stack Service) stack provisioning during test retrying.Why is it important?
Without these environment variables, retried FIPS integration test steps fail to provision ESS stacks correctly, causing test failures. This issue was discovered when investigating this failed build, where every retried FIPS step failed ESS stack provisioning due to the missing
EC_ENDPOINTconfiguration (at least this is my working theory).Interestingly, retried
fips:x86_64:sudo-false:fleetCI steps appeared successful, but further investigation revealed they don't actually run any tests, which masked the underlying issue.This fix ensures that all FIPS integration tests have the correct environment configuration regardless of whether they are initial runs or retried steps.
Checklist
./changelog/fragmentsusing the changelog toolDisruptive User Impact
No disruptive user impact. This change only affects the CI pipeline configuration and does not modify any user-facing functionality.
How to test this PR locally
This change affects the Buildkite CI pipeline configuration.
Related issues
N/A
This is an automatic backport of pull request #10943 done by Mergify.