Skip to content

ci: fix Ignite tests on ppc64le with IPv6 (backport)#22411

Merged
Croway merged 1 commit intocamel-4.18.xfrom
ci-fix/ignite-ipv6-ppc64le
Apr 2, 2026
Merged

ci: fix Ignite tests on ppc64le with IPv6 (backport)#22411
Croway merged 1 commit intocamel-4.18.xfrom
ci-fix/ignite-ipv6-ppc64le

Conversation

@Croway
Copy link
Copy Markdown
Contributor

@Croway Croway commented Apr 2, 2026

Summary

Backport of 03ad21d from main to camel-4.18.x.

All 53 Ignite tests fail consistently on ppc64le due to apache/ignite#10648 — Ignite generates a 471+ char work directory path by concatenating all IPv6 network interface names, exceeding filesystem limits. The fix overrides IGNITE_OVERRIDE_CONSISTENT_ID with a short name.

Already proven on main where Ignite tests pass since March 3.

Test plan

  • Verified fix matches main commit 03ad21d1084 exactly
  • CI passes on ppc64le (53 Ignite tests should go green)

Claude Code on behalf of Federico Mariani

Workaround for apache/ignite#10648
When IPv6 is used on Jenkins ppc64le, Ignite generates an excessively
long work directory path (471+ chars) by concatenating all network
interface names, causing IgniteCheckedException. Override the consistent
ID with a short name to avoid the path length limit.

Backport of 03ad21d from main branch.
@Croway Croway merged commit 3278a67 into camel-4.18.x Apr 2, 2026
3 checks passed
@davsclaus davsclaus deleted the ci-fix/ignite-ipv6-ppc64le branch April 12, 2026 04:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants