Killing action runner process should set running actions state to "abandoned" and not "failed"
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
In systemd hosts like U16 and EL7, running something like
st2 run core.local cmd="sleep 180; echo covfefe" timeout=300 -a; sleep 30; sudo systemctl stop st2actionrunner; sleep 10; st2 execution list
shows action status as ```failedand notabandoned``.
NOTE: This does not happen always. So I believe there is a race of some sort in U16.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the systemd scenario on the U16 or EL7 hosts using st2 run, stopping st2actionrunner, and checking st2 execution list. Investigate the intermittent shutdown race; done means actions interrupted by killing the runner are consistently reported as abandoned rather than failed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100