summaryrefslogtreecommitdiff
path: root/libpod/boltdb_state_internal.go
diff options
context:
space:
mode:
authorPaul Holzinger <pholzing@redhat.com>2021-11-10 20:54:01 +0100
committerPaul Holzinger <pholzing@redhat.com>2021-11-11 14:15:35 +0100
commitc43b81f9a0fbb08a3048dc687796ea38971382de (patch)
tree4276d8e48de11f4233b4008d54365f5a8bee4a24 /libpod/boltdb_state_internal.go
parent4bf0146c2978960b8c4dc5a9844c4948effbcfd2 (diff)
downloadpodman-c43b81f9a0fbb08a3048dc687796ea38971382de.tar.gz
podman-c43b81f9a0fbb08a3048dc687796ea38971382de.tar.bz2
podman-c43b81f9a0fbb08a3048dc687796ea38971382de.zip
Fix flake in upgrade tests
The cni plugins need access to /run/cni and the dnsname plugin needs access to /run/containers. The race condition was basically that a `podman stop` could either do the cleanup itself or the spawned cleanup process would do the cleanup if it was fast enough. The `podman stop` is executed on the host while the podman cleanup process is executed in the "parent container". The parent container contains older plugins than on the host. The dnsname plugin before version 1.3 could error and this would prevent CNI from doing a proper cleanup. The plugin errors because it could not find its files in /run/containers. On my system the test always failed because the cleanup process was always faster than the stop process. However in the CI VMs the stop process was usually faster and so it failed only sometimes. Fixes #11558 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Diffstat (limited to 'libpod/boltdb_state_internal.go')
0 files changed, 0 insertions, 0 deletions