automation-tests/pkg/domain/infra/tunnel
Daniel J Walsh 6ca721cccd
Drop container does not exist on removal to debugf
We have race conditions where a container can be removed
by two different processes when running podman --remove rm.

It can be cleaned up in the API or by the conmon executing
podman container cleanup.

When we fail to remove a container that does not exists we should
not be printing errors or warnings, we should just debug the fact.

[NO TESTS NEEDED] Since this is a race condition it is difficult to
test.

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
2021-05-21 09:37:53 -04:00
..
auto-update.go bump go module to v3 2021-02-22 09:03:51 +01:00
containers.go Drop container does not exist on removal to debugf 2021-05-21 09:37:53 -04:00
events.go bump go module to v3 2021-02-22 09:03:51 +01:00
generate.go Merge pull request #9445 from jmguzik/no-header-info-for-systemd-generation 2021-02-22 13:44:43 -05:00
healthcheck.go bump go module to v3 2021-02-22 09:03:51 +01:00
helpers.go bump go module to v3 2021-02-22 09:03:51 +01:00
images.go migrate Podman to containers/common/libimage 2021-05-05 11:30:12 +02:00
manifest.go Add support for podman manifest rm command 2021-05-19 17:32:02 -04:00
network.go Add network prune filters support to bindings 2021-04-10 00:21:35 +02:00
play.go add --mac-address to podman play kube 2021-05-04 20:14:13 +02:00
pods.go bump go module to v3 2021-02-22 09:03:51 +01:00
runtime.go Spelling 2020-12-22 13:34:31 -05:00
secrets.go bump go module to v3 2021-02-22 09:03:51 +01:00
system.go podman unshare: add --rootless-cni to join the ns 2021-04-07 15:54:12 +02:00
trust.go bump go module to v3 2021-02-22 09:03:51 +01:00
volumes.go bump go module to v3 2021-02-22 09:03:51 +01:00