podman error with nova container: stderr: standard_init_linux.go:203: exec user process caused \"no such file or directory\"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Emilien Macchi |
Bug Description
Based on the log this fails to get some images while some are there.
2018-11-19 21:42:01 | TASK [Debug output for task: Start containers for step 3] *******
2018-11-19 21:42:01 | fatal: [fedora-
2018-11-19 21:42:01 | "failed_
2018-11-19 21:42:01 | "outputs.
2018-11-19 21:42:01 | "$ podman inspect --type image --format exists docker.
2018-11-19 21:42:01 | "b'exists'",
2018-11-19 21:42:01 | "b''",
2018-11-19 21:42:01 | "$ podman inspect --type image --format exists docker.
2018-11-19 21:42:01| "b'error getting image \"docker.
Logstash confirms that this is a recurring issue:
http://
Changed in tripleo: | |
assignee: | nobody → Gabriele Cerami (gcerami) |
summary: |
- podman fails to find image: error getting image + podman error with nova container: stderr: standard_init_linux.go:203: + exec user process caused \"no such file or directory\" |
tags: | added: promotion-blocker |
Changed in tripleo: | |
milestone: | stein-2 → stein-3 |
The bug report is wrong, the job mentioned in the link failed because of this error: init_linux. go:203: exec user process caused \"no such file or directory\"
stderr: standard_
Also, the logstash URL is wrong as well. I have to admit it is confusing but the "error getting image" message isn't an error message that is critical to us, we should fix the operator experience I agree.
Let me investigate the "exec user process caused \"no such file or directory\"" issue, which is the real problem here.