2 Commits

Author	SHA1	Message	Date
Paul Holzinger	d633824a95	Instrument cleanup tracer to log weird volume removal flake ... Debug for #23913, I though if we have no idea which process is nuking the volume then we need to figure this out. As there is no reproducer we can (ab)use the cleanup tracer. Simply trace all unlink syscalls to see which process deletes our special named volume. Given the volume name is used as path on the fs and is deleted on volume rm we should know exactly which process deleted it the next time hopefully. Signed-off-by: Paul Holzinger <pholzing@redhat.com>	2024-10-30 18:50:07 +01:00
Paul Holzinger	0b59f67c3a	add epbf program to trace podman cleanup errors ... Add a new program based on bpftrace[1] to trace all podman processes with arguments and exit code/signals. Additionally this captures stderr from all podman container cleanup processes spawned by conmon which otherwise go to /dev/null and are never seen in any CI logs. Hopefull this allows us to debug strange network cleanup error seen in CI, my plan is to add this to the cirrus setup and upload the logs so we can check them when the flakes happen. [1] https://github.com/bpftrace/bpftrace Signed-off-by: Paul Holzinger <pholzing@redhat.com>	2024-09-24 12:47:03 +02:00