Skip to content

chore(camel-test-infra-hashicorp-vault): upgrade hashicorp.vault.container to 2.0.1#23355

Open
github-actions[bot] wants to merge 2 commits into
mainfrom
automated/upgrade-hashicorp-vault-container-2.0.1
Open

chore(camel-test-infra-hashicorp-vault): upgrade hashicorp.vault.container to 2.0.1#23355
github-actions[bot] wants to merge 2 commits into
mainfrom
automated/upgrade-hashicorp-vault-container-2.0.1

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

This PR updates the hashicorp.vault.container container image to version 2.0.1.

Update Details

  • Property: hashicorp.vault.container
  • Image: mirror.gcr.io/hashicorp/vault
  • File: /home/runner/work/camel/camel/test-infra/camel-test-infra-hashicorp-vault/src/main/resources/org/apache/camel/test/infra/hashicorp/vault/services/container.properties
  • Old version: 1.21.4
  • New version: 2.0.1

Verification

Please verify:

  • Container image version is compatible with existing tests
  • No breaking changes in the updated version
  • Tests pass with the new version

Run the following to rebuild the test infra:

mvn clean verify -pl camel-test-infra-hashicorp-vault

Then test the impacted components.


This PR was automatically created by the Container Version Upgrade workflow.

…ainer to 2.0.1

Update hashicorp.vault.container from 1.21.4 to 2.0.1
@github-actions github-actions Bot added dependencies Pull requests that update a dependency file container-images For check container upgrades automated For Check Container upgrade labels May 20, 2026
@apupier apupier self-assigned this May 20, 2026
@apupier
Copy link
Copy Markdown
Contributor

apupier commented May 20, 2026

note, the 2.0.0 wasn't working, see #22678

@apupier
Copy link
Copy Markdown
Contributor

apupier commented May 20, 2026

and now there is a different error when trying to start it:

Vault requires the IPC_LOCK capability. Please use --cap-add IPC_LOCK or add it to the securityContext capabilities
/usr/local/bin/docker-entrypoint.sh: exec: line 116: vault: Operation not permitted

@apupier
Copy link
Copy Markdown
Contributor

apupier commented May 20, 2026

which is a new requirement as mentioned hashicorp/vault#31919 (comment) :

 There are also new requirements on the IPC_LOCK capability being enabled since we have to set that at build time instead of runtime as we did before.

which is a new requirement since 2.0.1

Signed-off-by: Aurélien Pupier <apupier@ibm.com>
@apupier
Copy link
Copy Markdown
Contributor

apupier commented May 20, 2026

with the IPC_LOCK configured:

[�[1;34mINFO�[m] Running org.apache.camel.component.hashicorp.vault.integration.�[1mHashicorpVaultPropertiesSourceNoEnvTestIT�[m
[�[1;34mINFO�[m] �[1;32mTests run: �[0;1;32m25�[m, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.209 s -- in org.apache.camel.component.hashicorp.vault.integration.�[1mHashicorpVaultPropertiesSourceNoEnvTestIT�[m
[�[1;34mINFO�[m] Running org.apache.camel.component.hashicorp.vault.integration.operations.�[1mHashicorpProducerCreateMultiVersionSecretIT�[m
[�[1;34mINFO�[m] �[1;32mTests run: �[0;1;32m1�[m, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.523 s -- in org.apache.camel.component.hashicorp.vault.integration.operations.�[1mHashicorpProducerCreateMultiVersionSecretIT�[m
[�[1;34mINFO�[m] Running org.apache.camel.component.hashicorp.vault.integration.operations.�[1mHashicorpProducerCreateSecretIT�[m
[�[1;34mINFO�[m] �[1;32mTests run: �[0;1;32m1�[m, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.686 s -- in org.apache.camel.component.hashicorp.vault.integration.operations.�[1mHashicorpProducerCreateSecretIT�[m
[�[1;34mINFO�[m] Running org.apache.camel.component.hashicorp.vault.integration.operations.�[1mHashicorpProducerCreateSecretPOJOIT�[m
[�[1;34mINFO�[m] �[1;32mTests run: �[0;1;32m1�[m, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.888 s -- in org.apache.camel.component.hashicorp.vault.integration.operations.�[1mHashicorpProducerCreateSecretPOJOIT�[m
[�[1;34mINFO�[m] Running org.apache.camel.component.hashicorp.vault.integration.operations.�[1mHashicorpProducerDeleteSecretIT�[m
[�[1;34mINFO�[m] �[1;32mTests run: �[0;1;32m1�[m, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.891 s -- in org.apache.camel.component.hashicorp.vault.integration.operations.�[1mHashicorpProducerDeleteSecretIT�[m
[�[1;34mINFO�[m] Running org.apache.camel.component.hashicorp.vault.integration.operations.�[1mHashicorpProducerListSecretsIT�[m
[�[1;34mINFO�[m] �[1;32mTests run: �[0;1;32m1�[m, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.632 s -- in org.apache.camel.component.hashicorp.vault.integration.operations.�[1mHashicorpProducerListSecretsIT�[m
[�[1;34mINFO�[m] Running org.apache.camel.component.hashicorp.vault.integration.operations.�[1mHashicorpProducerReadMultiVersionedSecretIT�[m
[�[1;34mINFO�[m] �[1;32mTests run: �[0;1;32m1�[m, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.966 s -- in org.apache.camel.component.hashicorp.vault.integration.operations.�[1mHashicorpProducerReadMultiVersionedSecretIT�[m
[�[1;34mINFO�[m] Running org.apache.camel.component.hashicorp.vault.integration.operations.�[1mHashicorpProducerSecretPathHeaderIT�[m
[�[1;34mINFO�[m] �[1;32mTests run: �[0;1;32m1�[m, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.803 s -- in org.apache.camel.component.hashicorp.vault.integration.operations.�[1mHashicorpProducerSecretPathHeaderIT�[m
[�[1;34mINFO�[m] 
[�[1;34mINFO�[m] Results:
[�[1;34mINFO�[m] 
[�[1;34mINFO�[m] �[1;32mTests run: 32, Failures: 0, Errors: 0, Skipped: 0

@apupier apupier requested a review from oscerd May 20, 2026 10:07
@github-actions
Copy link
Copy Markdown
Contributor Author

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

  • First-time contributors require MANUAL approval for the GitHub Actions to run
  • You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
  • You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
  • Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

@github-actions
Copy link
Copy Markdown
Contributor Author

🧪 CI tested the following changed modules:

  • test-infra/camel-test-infra-hashicorp-vault
All tested modules (11 modules)
  • Camel :: Hashicorp :: Key Vault
  • Camel :: JBang :: MCP
  • Camel :: JBang :: Plugin :: Route Parser
  • Camel :: JBang :: Plugin :: TUI
  • Camel :: JBang :: Plugin :: Validate
  • Camel :: Launcher :: Container
  • Camel :: PQC
  • Camel :: Test Infra :: All test services
  • Camel :: Test Infra :: Hashicorp Vault
  • Camel :: YAML DSL :: Validator
  • Camel :: YAML DSL :: Validator Maven Plugin

⚙️ View full build and test results

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

Labels

automated For Check Container upgrade container-images For check container upgrades dependencies Pull requests that update a dependency file test-infra

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant