Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
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:
execute_robot_test recon <any test>
Ideally this should fail, since recon container is down. But all commands that reference the container are run with set +e in effect, so the container's unavailibility is basically ignored, and acceptance test passes.
Attachments
Issue Links
- links to