You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Siyao Meng (Jira)" <ji...@apache.org> on 2026/08/11 09:17:00 UTC
[jira] [Updated] (HDDS-15779) Add IPv6-only and dual-stack test coverage
[ https://issues.apache.org/jira/browse/HDDS-15779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siyao Meng updated HDDS-15779:
------------------------------
Description:
IPv6 parser unit tests are being added by the individual implementation tasks. This task owns the remaining component, integration, and end-to-end qualification needed before Ozone can claim dual-stack or IPv6-only support.
Required coverage:
* Preserve existing IPv4 behavior and defaults.
* Run dual-stack workflows over both IPv4 and IPv6 where the operating system supports both families.
* Run IPv6-only workflows with IPv4 routing unavailable so tests cannot fall back to IPv4.
* Treat an unavailable IPv6 environment as a skip, not a pass.
* Cover SCM and OM HA, leader changes, suggested-leader handling, client failover, Ratis role reporting, and Recon.
* Cover secure mode: Kerberos login and re-login, delegation tokens in both token-service modes, TLS identity checks, certificate renewal, KMS, service authorization, proxy-user rules, and IPv6 CIDR policies.
* Cover replicated writes and reads, active-write retries, and RS-3-2 erasure-coded write, read, degraded read, and reconstruction using at least six datanodes.
* Cover non-rolling upgrade followed by dual-stack to IPv6-only migration, rollback, SCM and OM peer identity retention, datanode UUID retention, container closure, and pipeline replacement.
* Cover OzoneFS, S3 Gateway, HTTPFS Gateway, administrative clients, metrics, and health endpoints.
* Record the Ozone commit, Hadoop and Ratis versions, JDK, operating system, network configuration, DNS records, and IPv4 availability.
The required CI environment must provide native IPv6-only networking, secure services, and enough datanodes for HA and erasure-coding reconstruction. GitHub-hosted runners do not currently provide native IPv6 connectivity.
Depends on HDDS-15772, the functional IPv6 tasks under this epic, and the dependency-release task.
Parent epic: HDDS-15763.
was:
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.
> 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
>
> IPv6 parser unit tests are being added by the individual implementation tasks. This task owns the remaining component, integration, and end-to-end qualification needed before Ozone can claim dual-stack or IPv6-only support.
> Required coverage:
> * Preserve existing IPv4 behavior and defaults.
> * Run dual-stack workflows over both IPv4 and IPv6 where the operating system supports both families.
> * Run IPv6-only workflows with IPv4 routing unavailable so tests cannot fall back to IPv4.
> * Treat an unavailable IPv6 environment as a skip, not a pass.
> * Cover SCM and OM HA, leader changes, suggested-leader handling, client failover, Ratis role reporting, and Recon.
> * Cover secure mode: Kerberos login and re-login, delegation tokens in both token-service modes, TLS identity checks, certificate renewal, KMS, service authorization, proxy-user rules, and IPv6 CIDR policies.
> * Cover replicated writes and reads, active-write retries, and RS-3-2 erasure-coded write, read, degraded read, and reconstruction using at least six datanodes.
> * Cover non-rolling upgrade followed by dual-stack to IPv6-only migration, rollback, SCM and OM peer identity retention, datanode UUID retention, container closure, and pipeline replacement.
> * Cover OzoneFS, S3 Gateway, HTTPFS Gateway, administrative clients, metrics, and health endpoints.
> * Record the Ozone commit, Hadoop and Ratis versions, JDK, operating system, network configuration, DNS records, and IPv4 availability.
> The required CI environment must provide native IPv6-only networking, secure services, and enough datanodes for HA and erasure-coding reconstruction. GitHub-hosted runners do not currently provide native IPv6 connectivity.
> Depends on HDDS-15772, the functional IPv6 tasks under this epic, and the dependency-release task.
> Parent epic: HDDS-15763.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org