Bug 2196229
| Summary: | tcmu-runner is not restarted automatically when it segfaults | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Raimund Sacherer <rsachere> |
| Component: | Cephadm | Assignee: | Adam King <adking> |
| Status: | CLOSED ERRATA | QA Contact: | Mohit Bisht <mobisht> |
| Severity: | high | Docs Contact: | Akash Raj <akraj> |
| Priority: | unspecified | ||
| Version: | 5.3 | CC: | adking, akraj, cephqe-warriors, idryomov, mcaldeir, mobisht, msaini, pnataraj, sostapov, tserlin, vereddy |
| Target Milestone: | --- | ||
| Target Release: | 5.3z4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-16.2.10-185.el8cp | Doc Type: | Bug Fix |
| Doc Text: |
.`tcmu-runner` process is now restarted on failure
Previously, for Cephadm iSCSI deployments, `tcmu-runner` and `rbd-target-api` were bundled into a single _systemd_ unit, with `rbd-target-api` being the primary process and `tcmu-runner` running in the background. Due to this, if the `tcmu-runner` process crashed, _systemd_ would not automatically attempt to restart it as it would only monitor the `rbd-target-api` process.
With this fix, `tcmu-runner` is automatically restarted with a script on crashing, unless there are too many crashes in short succession.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-07-19 16:19:10 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2210690 | ||
|
Comment 17
errata-xmlrpc
2023-07-19 16:19:10 UTC
|