[
https://issues.apache.org/jira/browse/HDDS-15779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18095036#comment-18095036
]
Siyao Meng commented on HDDS-15779:
-----------------------------------
Note: IIUC as of now (July 9, 2026) GitHub-hosted CI runner doesn't enable IPv6
by default. It needs to be manually enabled. And even when IPv6 is enabled, it
can only run dual-stack. IPv6-only CI is not possible with GitHub Actions
because runners require IPv4 to connect to GitHub's own Actions infra due to
the likes of pipelinesghubeus4.actions.githubusercontent.com only resolving to
IPv4 (https://github.com/orgs/community/discussions/10539). An IPv6-only
machine cannot register as a runner at all:
[https://github.com/actions/runner/issues/3138]
When we add CI to Ozone to test IPv6, we should be able to work around this
limitation by using dual-stack on runners but bind Ozone services to IPv6
addresses only so that it could still be properly tested.
> Add IPv6-only and dual-stack test coverage
> ------------------------------------------
>
> Key: HDDS-15779
> URL: https://issues.apache.org/jira/browse/HDDS-15779
> Project: Apache Ozone
> Issue Type: Task
> Reporter: Siyao Meng
> Priority: Major
>
> There is currently no IPv6 test coverage anywhere in the repo; parser tests
> use IPv4 only (TestHddsUtils, TestHddsServerUtil).
> Proposed:
> - Add IPv6-literal unit cases alongside each parser fix in this epic.
> - Stand up an IPv6-only (and dual-stack) MiniOzoneCluster or
> compose/acceptance scenario so RPC, HA, FS, and S3 paths are exercised end to
> end in CI.
> Depends on the JVM-stack change (HDDS-15772) landing first.
> Parent epic: HDDS-15763.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
