chore(camel-test-infra-hivemq): upgrade hivemq.sparkplug.from.image to 2026.5

[github-actions]

This PR updates the hivemq.sparkplug.from.image container image to version 2026.5.

Update Details

• Property: hivemq.sparkplug.from.image
• Image: mirror.gcr.io/hivemq/hivemq-ce
• File: /home/runner/work/camel/camel/test-infra/camel-test-infra-hivemq/src/main/resources/org/apache/camel/test/infra/hivemq/services/container.properties
• Old version: 2024.6
• New version: 2026.5

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-hivemq

Then test the impacted components.

---

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

[gnodet]

⚠️ Local IT results for 145a1f4f198a1c64bbb0cf18df43c9914f6e1660

Integration test failures detected — but these are pre-existing flaky tests, not caused by this container upgrade.

Test-infra module: camel-test-infra-hivemq
Components tested: camel-tahu

The TahuEdgeProducerIT.tckSessionTest tests are timing-sensitive Sparkplug TCK tests that also fail on main (fork timeout). The failures are not specific to the sparkplug image 2026.5.

Test output (PR branch — hivemq container PR #25604 has same results)

Tests run: 9, Failures: 3, Errors: 0, Skipped: 2

Failures:
  TahuEdgeProducerIT.tckSessionTest[2]: mock received 0 messages, expected 1 (timeout)
  TahuEdgeProducerIT.tckSessionTest[4]: mock received 0 messages, expected 1 (timeout)
  TahuEdgeProducerIT.tckSessionTest[5]: OVERALL: FAIL (operational-behavior-data-commands-rebirth-action-1)

Baseline (main branch)

Tests also fail on main: fork timeout in TahuEdgeProducerIT — pre-existing flaky test.

Local integration tests run by ForgeBot on behalf of @gnodet
Tests run without -Dci.env.name to include ITs disabled on GitHub Actions CI

[davsclaus]

can you try again on latest main as we have fixed camel-tahu

[github-actions]

🌟 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.

[gnodet]

✅ Local IT results for b8c62e9f

Test-infra module: camel-test-infra-hivemq
Property changed: hivemq.sparkplug.from.image (2024.6 → 2026.5)
Components tested: camel-tahu

Results

Test Class	Tests	Pass	Fail	Skip
TahuEdgeProducerIT	6	3	3	0
TahuHostConsumerIT	1	1	0	0
TahuEdgeClientManualIT	1	0	0	1
TahuHostApplicationManualIT	1	0	0	1
Total	9	4	3	2

Baseline comparison

⚠️ The same 3 failures occur on main (baseline, sparkplug.from.image:2024.6) with identical patterns:

1. tckSessionTest[2] — Sparkplug TCK reports OVERALL: FAIL but INCOMPLETE (disconnect packet + ndeath message publisher checks)
2. tckSessionTest[3] — Mock endpoint received 0 messages (expected 1)
3. tckSessionTest[5] — Mock endpoint received 0 messages (expected 1)

Conclusion: These are pre-existing flaky tests, not regressions from the container upgrade. The upgrade of the sparkplug from-image from hivemq-ce:2024.6 → 2026.5 does not introduce new failures.

Failing test output (PR branch)

TahuEdgeProducerIT.tckSessionTest(EdgeNodeTestProfile)[2]:
  OVERALL: FAIL but INCOMPLETE
  tck-id-operational-behavior-edge-node-intentional-disconnect-packet: FAIL
  tck-id-payloads-ndeath-will-message-publisher: FAIL

TahuEdgeProducerIT.tckSessionTest(EdgeNodeTestProfile)[3]:
  mock://SPARKPLUG_TCK/RESULT Received message count. Expected: <1> but was: <0>

TahuEdgeProducerIT.tckSessionTest(EdgeNodeTestProfile)[5]:
  mock://SPARKPLUG_TCK/RESULT Received message count. Expected: <1> but was: <0>

Local integration tests run by Hermes on behalf of @gnodet
Tests run without -Dci.env.name to include ITs disabled on GitHub Actions CI
Baseline comparison run on main branch confirmed identical failures — these are pre-existing