Siyao Meng created HDDS-16114:
---------------------------------
Summary: Avoid misleading Ozone mount warning in acceptance test
results
Key: HDDS-16114
URL: https://issues.apache.org/jira/browse/HDDS-16114
Project: Apache Ozone
Issue Type: Improvement
Reporter: Siyao Meng
h3. Problem
Acceptance tests use the {{ozone-runner}} image to generate Robot Framework
reports. The image entrypoint unconditionally prints:
{code}
To use Ozone please mount ozone folder to /opt/hadoop
{code}
Report generation does not use the Ozone binaries and therefore does not need
an {{/opt/hadoop}} mount.
When a test fails, {{acceptance.sh}} captures the line after {{FAIL}} for the
failure summary. The mount warning can therefore appear as the reported failure
reason, even though it is unrelated to the test failure.
Example: [CI
job|https://github.com/smengcl/hadoop-ozone/actions/runs/30975679630/job/92210943629]
h3. Root cause
{{run_rebot}} starts the {{ozone-runner}} image with its default entrypoint:
{code:bash}
docker run ... "${runner_image}" bash -c "rebot ..."
{code}
The image entrypoint prints the mount warning before executing the supplied
command.
h3. Proposed change
Override the image entrypoint with {{bash}} when running {{rebot}}:
{code:bash}
docker run ... --entrypoint bash "${runner_image}" \
-c "rebot ..."
{code}
This bypasses the generic Ozone startup message without adding an unnecessary
{{/opt/hadoop}} mount.
h3. Validation
* Run an acceptance test that generates Robot reports.
* Verify that {{log.html}} and {{report.html}} are generated.
* Verify that the Ozone mount warning is absent.
* Verify that an actual test failure is still reported correctly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
