Bug 1717199
| Summary: | ceph-mgr Segmentation fault in thread 7fa787013700 thread_name:prometheus | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Bob Emerson <roemerso> |
| Component: | Ceph-Mgr Plugins | Assignee: | Boris Ranto <branto> |
| Status: | CLOSED ERRATA | QA Contact: | Madhavi Kasturi <mkasturi> |
| Severity: | high | Docs Contact: | Erin Donnelly <edonnell> |
| Priority: | high | ||
| Version: | 3.2 | CC: | branto, ceph-eng-bugs, ceph-qe-bugs, edonnell, frederic.nass, gmeno, roemerso, schamilt, tchandra, tserlin, ukurundw, vumrao |
| Target Milestone: | z1 | ||
| Target Release: | 3.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-12.2.12 | Doc Type: | Bug Fix |
| Doc Text: |
.Using several `ceph-mgr` modules at the same time no longer causes random segmentation faults
Previously, random segmentation faults of the `ceph-mgr` daemon were occurring. This was because the shared memory in `ceph-mgr` Python modules was being accessed without proper locks, and the memory was not being dereferenced properly. For these cases, the locking mechanisms in `ceph-mgr` has been improved, and random segmentation faults when using several `ceph-mgr` modules at the same time no longer occurs.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-22 13:29:00 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: | 1726135 | ||
|
Comment 11
Christina Meno
2019-09-12 17:44:19 UTC
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:3173 |