Skip to content

Fix vault test container name collision across parameterized runs#68947

Open
dwoz wants to merge 3 commits intosaltstack:3006.xfrom
dwoz:3006.x-test-check
Open

Fix vault test container name collision across parameterized runs#68947
dwoz wants to merge 3 commits intosaltstack:3006.xfrom
dwoz:3006.x-test-check

Conversation

@dwoz
Copy link
Copy Markdown
Contributor

@dwoz dwoz commented Apr 16, 2026

The vault_container_version fixture uses a hardcoded container name "vault" for all three parameterized versions (0.9.6, 1.3.1, latest). When the container from a prior parameterized run isn't fully removed before the next one starts, Docker returns a 409 Conflict. Use random_string to generate unique container names per run.

The vault_container_version fixture uses a hardcoded container name
"vault" for all three parameterized versions (0.9.6, 1.3.1, latest).
When the container from a prior parameterized run isn't fully removed
before the next one starts, Docker returns a 409 Conflict. Use
random_string to generate unique container names per run.
@dwoz dwoz requested a review from a team as a code owner April 16, 2026 01:20
@dwoz dwoz added the test:full Run the full test suite label Apr 16, 2026
twangboy
twangboy previously approved these changes Apr 16, 2026
Same fix as the functional vault tests - use random_string for
the Docker container name to avoid 409 conflicts when parameterized
fixture teardown overlaps with the next setup.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test:full Run the full test suite

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants