https://tracker.ceph.com/https://tracker.ceph.com/favicon.ico2020-06-25T23:58:33ZCeph RADOS - Bug #46216: mon: log entry with garbage generated by bad memory accesshttps://tracker.ceph.com/issues/46216?journal_id=1690802020-06-25T23:58:33ZPatrick Donnellypdonnell@redhat.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-1 priority-4 priority-default" href="/issues/45331">Bug #45331</a>: Segmentation fault</i> added</li></ul> RADOS - Bug #46216: mon: log entry with garbage generated by bad memory accesshttps://tracker.ceph.com/issues/46216?journal_id=1693742020-06-30T16:41:55ZNeha Ojhanojha@redhat.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Fix Under Review</i></li><li><strong>Pull request ID</strong> set to <i>35784</i></li></ul> RADOS - Bug #46216: mon: log entry with garbage generated by bad memory accesshttps://tracker.ceph.com/issues/46216?journal_id=1693822020-06-30T17:37:45ZPatrick Donnellypdonnell@redhat.com
<ul><li><strong>Status</strong> changed from <i>Fix Under Review</i> to <i>Pending Backport</i></li></ul> RADOS - Bug #46216: mon: log entry with garbage generated by bad memory accesshttps://tracker.ceph.com/issues/46216?journal_id=1694072020-07-01T02:51:08ZPatrick Donnellypdonnell@redhat.com
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-3 priority-4 priority-default closed" href="/issues/46286">Backport #46286</a>: octopus: mon: log entry with garbage generated by bad memory access</i> added</li></ul> RADOS - Bug #46216: mon: log entry with garbage generated by bad memory accesshttps://tracker.ceph.com/issues/46216?journal_id=1694092020-07-01T02:51:15ZPatrick Donnellypdonnell@redhat.com
<ul><li><strong>Copied to</strong> <i><a class="issue tracker-9 status-6 priority-4 priority-default closed" href="/issues/46287">Backport #46287</a>: nautilus: mon: log entry with garbage generated by bad memory access</i> added</li></ul> RADOS - Bug #46216: mon: log entry with garbage generated by bad memory accesshttps://tracker.ceph.com/issues/46216?journal_id=1766172020-10-03T02:04:24ZNathan Cutlerncutler@suse.cz
<ul><li><strong>Status</strong> changed from <i>Pending Backport</i> to <i>Resolved</i></li></ul><p>While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".</p>