HDDS-16114. Avoid misleading Ozone mount warning in acceptance test results - #10979
Draft
smengcl wants to merge 1 commit into
Draft
HDDS-16114. Avoid misleading Ozone mount warning in acceptance test results#10979smengcl wants to merge 1 commit into
smengcl wants to merge 1 commit into
Conversation
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
The acceptance test helper uses the Ozone runner image to combine Robot Framework results with
rebot.The runner image's default entrypoint expects Ozone to be mounted at
/opt/hadoop. Report aggregation does not need that mount, but the entrypoint still emits:This change overrides the container entrypoint with
bashand passes the existingrebotcommand through-c. This bypasses the irrelevant mount check while preserving the existing volumes, working directory, command, and output handling.What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-16114
How was this patch tested?
Fork CI was run at commit
026dd7ce2ab029da87c023bae532d014a364a51a:https://github.com/smengcl/hadoop-ozone/actions/runs/31296676320/attempts/2
All acceptance jobs passed after retry, including:
The complete logs for these jobs confirm that
rebotgenerated the combined XML files and finallog.htmlandreport.html. None of the logs contains the/opt/hadoopmount warning.The first attempt had SCM safe-mode startup timeouts in the EC and misc acceptance jobs. Both jobs passed on retry, confirming that those failures were transient and unrelated to this change.
The rerun recorded 42 successful and 2 skipped jobs. The remaining non-green jobs were unrelated integration-test results:
integration (om)failed inTestOMRatisSnapshots.testInstallSnapshotWithClientWritebecause an expected snapshot was null.integration (flaky)was cancelled after hanging inTestBlockOutputStreamWithFailures.Generated-by: Codex (GPT-5)