-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
pkg/rootless: correctly handle proxy signals on reexec
There are quite a lot of places in podman were we have some signal handlers, most notably libpod/shutdown/handler.go. However when we rexec we do not want any of that and just send all signals we get down to the child obviously. So before we install our signal handler we must first reset all others with signal.Reset(). Also while at it fix a problem were the joinUserAndMountNS() code path would not forward signals at all. This code path is used when you have running containers but the pause process was killed. Fixes #16091 Given that signal handlers run in different goroutines parallel it would explain why it flakes sometimes in CI. However to my understanding this flake can only happen when the pause process is dead before we run the podman command. So the question still is what kills the pause process? Signed-off-by: Paul Holzinger <[email protected]>
- Loading branch information
Showing
4 changed files
with
126 additions
and
58 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,50 @@ | ||
# -*- bash -*- | ||
# | ||
# BATS helpers for sig-proxy functionality | ||
# | ||
|
||
# Command to run in each of the tests. | ||
SLEEPLOOP='trap "echo BYE;exit 0" INT;echo READY;while :;do sleep 0.1;done' | ||
|
||
# Main test code: wait for container to exist and be ready, send it a | ||
# signal, wait for container to acknowledge and exit. | ||
function _test_sigproxy() { | ||
local cname=$1 | ||
local kidpid=$2 | ||
|
||
# Wait for container to appear | ||
local timeout=10 | ||
while :;do | ||
sleep 0.5 | ||
run_podman '?' container exists $cname | ||
if [[ $status -eq 0 ]]; then | ||
break | ||
fi | ||
timeout=$((timeout - 1)) | ||
if [[ $timeout -eq 0 ]]; then | ||
run_podman ps -a | ||
die "Timed out waiting for container $cname to start" | ||
fi | ||
done | ||
|
||
# Now that container exists, wait for it to declare itself READY | ||
wait_for_ready $cname | ||
|
||
# Signal, and wait for container to exit | ||
kill -INT $kidpid | ||
timeout=20 | ||
while :;do | ||
sleep 0.5 | ||
run_podman logs $cname | ||
if [[ "$output" =~ BYE ]]; then | ||
break | ||
fi | ||
timeout=$((timeout - 1)) | ||
if [[ $timeout -eq 0 ]]; then | ||
run_podman ps -a | ||
die "Timed out waiting for BYE from container" | ||
fi | ||
done | ||
|
||
run_podman rm -f -t0 $cname | ||
} |