We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We are seeing flakey builds for the vault integration tests that look like:
[2021-03-10T16:20:49.965Z] + docker-compose run --rm -T -e VAULT_ADDR=http://vault:8200 -e VAULT_TOKEN=s.tx9QsSG4Vj1zW6V5q40slxuS --entrypoint vault vault secrets enable -version=1 kv [2021-03-10T16:20:51.857Z] Creating e5b9e7_vault_run ... [2021-03-10T16:20:52.432Z] Creating e5b9e7_vault_run ... done [2021-03-10T16:21:10.561Z] Error enabling: Error making API request. [2021-03-10T16:21:10.561Z] [2021-03-10T16:21:10.561Z] URL: POST http://vault:8200/v1/sys/mounts/kv [2021-03-10T16:21:10.561Z] Code: 400. Errors: [2021-03-10T16:21:10.561Z] [2021-03-10T16:21:10.561Z] * path is already in use at kv/ [2021-03-10T16:21:10.561Z] 2
See Jenkins
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We are seeing flakey builds for the vault integration tests that look like:
See Jenkins
The text was updated successfully, but these errors were encountered: