diff options
| author | Adrian Reber <areber@redhat.com> | 2021-10-13 12:59:01 +0000 |
|---|---|---|
| committer | Adrian Reber <areber@redhat.com> | 2021-10-14 18:53:32 +0000 |
| commit | 8439a6d5ee53020575bd79ae00c2a222213ad112 (patch) | |
| tree | 537ab20c173c158bd048414644045af6a4d71570 /libpod/network | |
| parent | 1c156f22678b3f476ea78fa9e22982c66a7e1559 (diff) | |
| download | podman-8439a6d5ee53020575bd79ae00c2a222213ad112.tar.gz podman-8439a6d5ee53020575bd79ae00c2a222213ad112.tar.bz2 podman-8439a6d5ee53020575bd79ae00c2a222213ad112.zip | |
Checkpoint/Restore test fixes
Moving to Fedora 35 showed test failures (time outs) in the test
"podman checkpoint and restore container with different port mappings"
The test starts a container and maps the internal port 6379 to the local
port 1234 ('-p 1234:6379') and then tries to connect to localhost:1234
On Fedora 35 this failed and blocked the test because the container was
not yet ready. The test was trying to connect to localhost:1234 but
nothing was running there. So the error was not checkpointing related.
Before trying to connect to the container the test is now waiting for
the container to be ready.
Another problem with this test and running ginkgo in parallel was that
it was possible that the port was already in use. Now for each run a
random port is selected to decrease the chance of collisions.
Signed-off-by: Adrian Reber <areber@redhat.com>
Diffstat (limited to 'libpod/network')
0 files changed, 0 insertions, 0 deletions