Open
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
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 changed
This changes the bare-metal GitHub Actions concurrency groups to a fixed global key:
ci-e2e-baremetal-global.Why
The previous concurrency keys were based on
${{ github.ref }}, which serialized runs only per PR ref. That still allowed bare-metal e2e jobs from different PRs to run at the same time against the sharedci-pool.That overlap can cause host reuse and cross-run interference. In the March 26, 2026 failure on PR #1850, one bare-metal run observed a hostname from another workflow run, which is consistent with concurrent use of the same bare-metal pool.
Scope
This only changes bare-metal workflows:
E2E PR Blockingbare-metal jobE2E Basic BaremetalE2E Baremetal FeatureHcloud-only jobs keep their existing per-ref concurrency.
Matching
v1.1.xPR: #1908