Actions
Bug #42082
closedpybind/rados: set_omap() crash on py3
% Done:
0%
Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42083: nautilus: pybind/rados: set_omap() crash on py3 added
Updated by Brad Hubbard over 4 years ago
- Is duplicate of Bug #41618: 14.2.1->14.2.2 ceph-mgr hard segfault. devicehealth? added
Updated by Brad Hubbard over 4 years ago
- Status changed from Pending Backport to Duplicate
Updated by Brad Hubbard over 4 years ago
- Is duplicate of deleted (Bug #41618: 14.2.1->14.2.2 ceph-mgr hard segfault. devicehealth?)
Updated by Brad Hubbard over 4 years ago
- Has duplicate Bug #41618: 14.2.1->14.2.2 ceph-mgr hard segfault. devicehealth? added
Updated by Brad Hubbard over 4 years ago
- Status changed from Duplicate to Pending Backport
Updated by Brad Hubbard over 4 years ago
- Related to Bug #42680: crash in in thread 7f6a445ee700 thread_name:devicehealth added
Updated by Nathan Cutler over 4 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions