canonical / canonical/spread

Politely terminating processes with kill hangs the VM backend

Open
#171 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
127
Forks
81
PR merge metrics
No merged PRs in 30d

Description

Using a QEMU backend on a amd64 host, using `kill -s TERM` or equivalent to kill a running process from the spread shell, a test script inside the VM (or anything else as far as I know) results in the whole VM hanging then displaying this message and exiting:

```
2023-06-06 11:39:17 Error running debug shell: wait: remote command exited without exit status or exit signal
```

Note that `kill -s KILL` still works as expected.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the issue with the QEMU backend on an amd64 host, terminating a running process with TERM and then KILL for comparison. Trace how the VM backend handles the remote command's termination and verify that TERM no longer hangs or exits without status, while KILL continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
infrastructure, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.