podman/pkg/bindings/test
Paul Holzinger 19aabf440e
remote: exec inspect update exec session status
The remote API will wait 300s by default before conmon will call the
cleanup. In the meantime when you inspect an exec session started with
ExecStart() (so not attached) and it did exit we do not know that. If
a caller inspects it they think it is still running. To prevent this we
should sync the session based on the exec pid and update the state
accordingly.

For a reproducer see the test in this commit or the issue.

Fixes #18424

Signed-off-by: Paul Holzinger <pholzing@redhat.com>
2023-05-03 14:54:00 +02:00
..
fixture Add guard for BuildOptions.CommonBuildOpts 2021-09-30 14:30:06 -07:00
attach_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
auth_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
common_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
connection_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
containers_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
create_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
exec_test.go remote: exec inspect update exec session status 2023-05-03 14:54:00 +02:00
generator_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
images_test.go ginkgo v2: remove CurrentGinkgoTestDescription() 2023-05-02 11:27:36 +02:00
info_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
manifests_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
networks_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
pods_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
resource_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
secrets_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
system_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
test_suite_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
types_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00
volumes_test.go update to ginkgo v2 2023-05-02 11:27:35 +02:00