jojochuang commented on PR #11510: URL: https://github.com/apache/ozone/pull/11510#issuecomment-6180748046
## CI failure analysis (HA-unsecure, `test-ipv6.sh`) Fork run [smengcl/hadoop-ozone/actions/runs/38373381842](https://github.com/smengcl/hadoop-ozone/actions/runs/38373381842) / job `115330662593`: the **HA-unsecure** acceptance job failed only on **`compose/ozone-ha/test-ipv6.sh`**. Other scripts in the same job (`test.sh`, `test-haproxy-s3g.sh`, etc.) passed. ### Symptom - `start_docker_env` never gets past `wait_for_port scm1 9860` (120s) → `Timed out waiting on scm1 9860 to become available`. - Logs repeat `service "scm1" is not running` (container exits during init, not a Robot failure). ### Root cause From artifact `ozone-ha/ipv6/docker-ozone-ha-scm1-1.log`, SCM aborts on **`ozone scm --init`** because the **JaCoCo `-javaagent`** fails in `premain`: ``` Caused by: java.net.SocketException: Network is unreachable at org.jacoco.agent.rt.internal_bac9136.output.TcpClientOutput.createSocket(...) ... Aborted (core dumped) /opt/hadoop/bin/ozone scm --init ``` This job runs with **`with-coverage: true`**, so every JVM loads JaCoCo and opens a TCP socket to the coverage collector. On the **IPv6-only** compose network (`enable_ipv4: false`), that collector address is not reachable (no IPv4 path), the agent fails to load, and SCM never binds **9860**. So this looks like **coverage × IPv6-only compose**, not a missing Ozone bind key in the first instance—the default HA scripts still use an IPv4-enabled bridge where JaCoCo works. ### Suggested directions 1. Disable or skip JaCoCo for `test-ipv6.sh` when `OZONE_WITH_COVERAGE=true` (override `JAVA_TOOL_OPTIONS` / jacoco opts for that script only). 2. Configure JaCoCo to report to an address reachable on the IPv6 bridge (if supported). 3. Run IPv6 acceptance in a **separate suite without coverage** until (1) or (2) is in place. Happy to re-review once CI is green with one of these approaches. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
