Skip to content

chore(camel-test-infra-milvus): upgrade milvus.container to v2.6.11#21893

Merged
gnodet merged 4 commits intomainfrom
automated/upgrade-milvus-container-v2.6.11-18
Mar 13, 2026
Merged

chore(camel-test-infra-milvus): upgrade milvus.container to v2.6.11#21893
gnodet merged 4 commits intomainfrom
automated/upgrade-milvus-container-v2.6.11-18

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

This PR updates the milvus.container container image to version v2.6.11.

Update Details

  • Property: milvus.container
  • Image: mirror.gcr.io/milvusdb/milvus
  • File: /home/runner/work/camel/camel/test-infra/camel-test-infra-milvus/src/main/resources/org/apache/camel/test/infra/milvus/services/container.properties
  • Old version: v2.5.11
  • New version: v2.6.11

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 verify:

mvn clean verify -pl camel-test-infra-milvus

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

Update milvus.container from v2.5.11 to v2.6.11
@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 Mar 10, 2026
@gnodet
Copy link
Copy Markdown
Contributor

gnodet commented Mar 10, 2026

/component-test camel-ai

@gnodet
Copy link
Copy Markdown
Contributor

gnodet commented Mar 10, 2026

/component-test camel-ai

Result ✅ The tests passed successfully

@github-actions
Copy link
Copy Markdown
Contributor Author

🤖 The Apache Camel test robot will run the tests for you 👍

@gnodet
Copy link
Copy Markdown
Contributor

gnodet commented Mar 10, 2026

/component-test camel-ai

Copy link
Copy Markdown
Contributor

@apupier apupier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

error locally:

[�[1;31mERROR�[m] �[1;31mTests �[0;1mrun: �[0;1m1�[m, Failures: 0, �[1;31mErrors: �[0;1;31m1�[m, Skipped: 0, Time elapsed: 294.4 s�[1;31m <<< FAILURE!�[m -- in org.apache.camel.component.milvus.�[1mMilvusCreateCollectionTest�[m
[�[1;31mERROR�[m] org.apache.camel.component.milvus.MilvusCreateCollectionTest -- Time elapsed: 294.4 s <<< ERROR!
org.testcontainers.containers.ContainerLaunchException: Container startup failed for image mirror.gcr.io/milvusdb/milvus:v2.6.11
	at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:346)
	at org.testcontainers.containers.GenericContainer.start(GenericContainer.java:317)
	at org.apache.camel.test.infra.milvus.services.MilvusLocalContainerInfraService.initialize(MilvusLocalContainerInfraService.java:84)
	at org.apache.camel.test.infra.common.services.SingletonService.doInitializeService(SingletonService.java:55)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at org.apache.camel.test.infra.common.services.SingletonService.addToStore(SingletonService.java:48)
	at org.apache.camel.test.infra.common.services.SingletonService.beforeAll(SingletonService.java:61)
	at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:387)
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1312)
	at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1843)
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1808)
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:188)
	Suppressed: java.lang.NullPointerException: Cannot invoke "org.apache.camel.test.junit6.CamelContextManager.stop()" because "this.contextManager" is null
		at org.apache.camel.test.junit6.ContextManagerExtension.afterAll(ContextManagerExtension.java:77)
		... 5 more
Caused by: org.rnorth.ducttape.RetryCountExceededException: Retry limit hit with exception
	at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:88)
	at org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:331)
	... 11 more
Caused by: org.testcontainers.containers.ContainerLaunchException: Could not create/start container
	at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:551)
	at org.testcontainers.containers.GenericContainer.lambda$doStart$0(GenericContainer.java:341)
	at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:81)
	... 12 more
Caused by: java.lang.IllegalStateException: Wait strategy failed. Container exited with code 134
	at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:520)
	... 14 more
Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for URL to be accessible (http://localhost:40247/healthz should return HTTP 200)
	at org.testcontainers.containers.wait.strategy.HttpWaitStrategy.waitUntilReady(HttpWaitStrategy.java:320)
	at org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)
	at org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:904)
	at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:487)
	... 14 more
Caused by: org.rnorth.ducttape.TimeoutException: Timeout waiting for result with exception
	at org.rnorth.ducttape.unreliables.Unreliables.retryUntilSuccess(Unreliables.java:54)
	at org.testcontainers.containers.wait.strategy.HttpWaitStrategy.waitUntilReady(HttpWaitStrategy.java:252)
	... 17 more
Caused by: java.lang.RuntimeException: java.net.ConnectException: Connection refused
	at org.testcontainers.containers.wait.strategy.HttpWaitStrategy.lambda$waitUntilReady$6(HttpWaitStrategy.java:312)
	at org.rnorth.ducttape.ratelimits.RateLimiter.doWhenReady(RateLimiter.java:27)
	at org.testcontainers.containers.wait.strategy.HttpWaitStrategy.lambda$waitUntilReady$7(HttpWaitStrategy.java:257)
	at org.rnorth.ducttape.unreliables.Unreliables.lambda$retryUntilSuccess$0(Unreliables.java:43)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.net.ConnectException: Connection refused
	at java.base/sun.nio.ch.Net.connect0(Native Method)
	at java.base/sun.nio.ch.Net.connect(Net.java:589)
	at java.base/sun.nio.ch.Net.connect(Net.java:578)
	at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:583)
	at java.base/java.net.Socket.connect(Socket.java:751)
	at java.base/java.net.Socket.connect(Socket.java:686)
	at java.base/sun.net.NetworkClient.doConnect(NetworkClient.java:183)
	at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:531)
	at java.base/sun.net.www.http.HttpClient.openServer(HttpClient.java:636)
	at java.base/sun.net.www.http.HttpClient.<init>(HttpClient.java:282)
	at java.base/sun.net.www.http.HttpClient.New(HttpClient.java:386)
	at java.base/sun.net.www.http.HttpClient.New(HttpClient.java:408)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:1324)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1257)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1143)
	at java.base/sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:1072)
	at org.testcontainers.containers.wait.strategy.HttpWaitStrategy.lambda$waitUntilReady$6(HttpWaitStrategy.java:274)
	... 7 more

@gnodet
Copy link
Copy Markdown
Contributor

gnodet commented Mar 10, 2026

/component-test camel-ai

Result ❌ The tests failed please check the logs

@gnodet
Copy link
Copy Markdown
Contributor

gnodet commented Mar 10, 2026

/update-branch

@github-actions
Copy link
Copy Markdown
Contributor Author

✅ Branch updated successfully by merging main.

@gnodet
Copy link
Copy Markdown
Contributor

gnodet commented Mar 10, 2026

/component-test camel-ai

@github-actions
Copy link
Copy Markdown
Contributor Author

/component-test camel-ai tests failed. Please check the logs.

@gnodet
Copy link
Copy Markdown
Contributor

gnodet commented Mar 10, 2026

/update-branch

@github-actions
Copy link
Copy Markdown
Contributor Author

✅ Branch updated successfully by merging main.

@gnodet
Copy link
Copy Markdown
Contributor

gnodet commented Mar 10, 2026

/component-test camel-ai

@github-actions
Copy link
Copy Markdown
Contributor Author

/component-test camel-ai tests failed. Please check the logs.

⚠️ Some integration tests are disabled on GitHub Actions (@DisabledIfSystemProperty(named = "ci.env.name")) and require manual verification:

  • components/camel-ai: 34 test(s) disabled on GitHub Actions

@gnodet
Copy link
Copy Markdown
Contributor

gnodet commented Mar 10, 2026

Local test results for Milvus v2.6.11:

The Milvus v2.6.11 container fails to start — both on GitHub Actions and locally. The container crashes with exit code 134 (SIGABRT) during startup. This is a v2.5 → v2.6 major version jump that likely introduces breaking changes or new infrastructure requirements.

This PR is not safe to merge in its current state. The container version upgrade needs investigation into what changed in Milvus v2.6 (e.g., new dependencies like etcd/MinIO configuration, changed startup requirements, etc.).

Milvus v2.6+ requires DEPLOY_MODE=STANDALONE environment variable when
running in standalone mode with embedded etcd. Without it, the container
panics with "embedded etcd can not be used under distributed mode".

This mirrors the fix already applied in testcontainers-dotnet (PR #1569).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@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 build-all, build-dependents, 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.

@gnodet
Copy link
Copy Markdown
Contributor

gnodet commented Mar 10, 2026

I've verified the Milvus v2.6.11 upgrade locally with Docker — all 7 integration tests pass.

Issue: Milvus v2.6+ requires the DEPLOY_MODE=STANDALONE environment variable when running in standalone mode with embedded etcd. Without it, the container panics with embedded etcd can not be used under distributed mode (exit code 134/SIGABRT).

Fix: The additional commit (f7d3b8a) adds withEnv("DEPLOY_MODE", "STANDALONE") to the MilvusLocalContainerInfraService container setup. This mirrors the same fix already applied in testcontainers-dotnet PR #1569. The testcontainers-java MilvusContainer doesn't set this yet, so we add it in Camel's test infra.

@apupier could you double-check locally if you have a chance? The CI build passes (JDK 21 + JDK 25).

@gnodet gnodet requested a review from apupier March 11, 2026 10:27
Copy link
Copy Markdown
Contributor

@gnodet gnodet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified locally — all 7 MilvusComponentIT tests pass with Milvus v2.6.11. The DEPLOY_MODE=STANDALONE env var addition is correct for the new container version.

Copy link
Copy Markdown
Contributor

@apupier apupier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tested locally and works fine

@gnodet gnodet merged commit c970c29 into main Mar 13, 2026
4 checks passed
@apupier apupier deleted the automated/upgrade-milvus-container-v2.6.11-18 branch March 20, 2026 15:26
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.

3 participants