You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Attila Doroszlai (Jira)" <ji...@apache.org> on 2020/01/17 19:18:00 UTC
[jira] [Updated] (HDDS-2902) execute_robot_test on
unknown/unavailable container should fail acceptance test
[ https://issues.apache.org/jira/browse/HDDS-2902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Attila Doroszlai updated HDDS-2902:
-----------------------------------
Summary: execute_robot_test on unknown/unavailable container should fail acceptance test (was: execute_robot_test on unknown container should fail acceptance test)
> execute_robot_test on unknown/unavailable container should fail acceptance test
> -------------------------------------------------------------------------------
>
> Key: HDDS-2902
> URL: https://issues.apache.org/jira/browse/HDDS-2902
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: test
> Reporter: Attila Doroszlai
> Assignee: Attila Doroszlai
> Priority: Major
>
> Before the fix for HDDS-2897, {{recon}} container in {{ozonesecure}} environment exited with error soon after start. While working on the fix [~avijayan] noticed that the following test case (which tries to run some test on {{recon}} container) does not catch this error:
> {code}
> execute_robot_test recon <any test>
> {code}
> Ideally this should fail, since {{recon}} container is down. But all commands that reference the container are run with [{{set +e}} in effect|https://github.com/apache/hadoop-ozone/blob/1caf1e30865aa2b380a7fca6d87f5ae8034fee4e/hadoop-ozone/dist/src/main/compose/testlib.sh#L99-L107], so the container's unavailibility is basically ignored, and acceptance test passes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org