action #91488
closed
containers: openqa test "single_container_webui" eventually fails
Added by ilausuch about 3 years ago.
Updated almost 3 years ago.
Category:
Regressions/Crashes
Description
Motivation¶
Sometimes we could see this error
Error: No such container: openqa_webui
This is because the docker run has executed without problems, but one moment later the container doesn't exist
assert_script_run("docker run --rm -d --network testing $volumes $certificates -p 80:80 --name openqa_webui openqa_webui");
wait_for_container_log("openqa_webui", "Web application available at", "docker");
Examples:
We don't have information to know what is the problem
Acceptance Criteria¶
- AC 1: Log information when this crashes
- AC 2: Fix the problem
Related issues
1 (1 open — 0 closed)
Maybe we can extend wait_for_container_log to show all logs in case of a failure? To see if the container got deleted, crashed or whatever 🤔️
An alternative idea, we also could use a volume for logs
-v logs:/var/log
This is not removed when the container is removed
- Status changed from New to Feedback
- Target version set to Ready
- Related to action #91818: containers: Add logs when docker-compose up fails in the CI added
- Status changed from Feedback to Resolved
Last comment could conclude that the code to print the logs to know why the container doesn't initialize is working and show us the causes of failures for this test. As all these weeks of observation only mentioned errors has detected and are not related with the code of this tests of the containers code. So we conclude we can resolve this ticket, knowing that if in the future we will know the reasons for new failures.
Also available in: Atom
PDF