Failing to stop nmeof-gw container when removing nvmeof-gw service resulting SIGKILL nvmeof-gw systemd service
- Dominant language
- Python
- Stars
- 132
- Forks
- 69
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 47
Description
Removing nvmeof-gw -
`ceph orch rm nvmeof.nvmeof-pool --force`
Resulting systemd service exit code 137 (128+9) ==> SIGKILL:
```
Feb 26 08:23:50 a-rhel9-node2 bash[1771785]: time="2024-02-26T08:23:50-05:00" level=warning msg="StopSignal SIGTERM failed to stop container ceph-ec7951fe-d263-11ee-8562-005056b4ea89-nvmeof-nvmeof-pool-a-rhel9-node2-dfydij in 10 seconds, resorting to SIGKILL"
.....
Feb 26 08:23:50 a-rhel9-node2 systemd[1]: ceph-ec7951fe-d263-11ee-8562-005056b4ea89@nvmeof.nvmeof-pool.a-rhel9-node2.dfydij.service: Main process exited, code=exited, status=137/n/a
Feb 26 08:23:50 a-rhel9-node2 systemd[1]: ceph-ec7951fe-d263-11ee-8562-005056b4ea89@nvmeof.nvmeof-pool.a-rhel9-node2.dfydij.service: Failed with result 'exit-code'.
Feb 26 08:23:50 a-rhel9-node2 systemd[1]: Stopped Ceph nvmeof.nvmeof-pool.a-rhel9-node2.dfydij for ec7951fe-d263-11ee-8562-005056b4ea89.
```
Contributor guide
Research direction
No source files or tests are named. Reproduce the issue with `ceph orch rm nvmeof.nvmeof-pool --force`, then trace the nvmeof-gw container and systemd service shutdown handling; done means removal stops the service cleanly without SIGKILL or exit status 137.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100