Bug 1670781
Summary: | mgr: fix crash due to multiple sessions from daemons with same name | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Boris Ranto <branto> |
Component: | RADOS | Assignee: | Boris Ranto <branto> |
Status: | CLOSED ERRATA | QA Contact: | Vasishta <vashastr> |
Severity: | medium | Docs Contact: | Bara Ancincova <bancinco> |
Priority: | unspecified | ||
Version: | 3.2 | CC: | branto, ceph-eng-bugs, dzafman, edonnell, jdurgin, kchai, nojha, tchandra, tserlin, vumrao |
Target Milestone: | z1 | ||
Target Release: | 3.2 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | RHEL: ceph-12.2.8-64.el7cp Ubuntu: ceph_12.2.8-49redhat1 | Doc Type: | Bug Fix |
Doc Text: |
.Ceph Manager no longer crashes when two or more Ceph Object Gateway daemons use the same name
Previously, when two or more Ceph Object Gateway daemons used the same name in a cluster, Ceph Manager terminated unexpectedly. The underlying source code has been modified, and Ceph Manager no longer crashes in the described scenario.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-03-07 15:51:30 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: | 1584264, 1629656 |
Description
Boris Ranto
2019-01-30 11:02:32 UTC
Thanks for taking care of this Boris! *** Bug 1634964 has been marked as a duplicate of this bug. *** No problem, I knew we had another bugzilla downstream for this but I just couldn't find it, thanks for linking it! Followed steps mentioned in Comment 7 , working fine with ceph-12.2.8-77 Moving to VERIFIED state. Regards, Vasishta Shastry QE, Ceph 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:0475 |