Bug #48929: Listing a new, empty omap datalog errors - rgw - Ceph

Actions

Bug #48929

closed

Listing a new, empty omap datalog errors

Added by Adam Emerson over 3 years ago. Updated about 3 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Target version:

-

% Done:

0%

Source:

Q/A

Tags:

Backport:

pacific

Regression:

No

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

On −ENOENT, we should return 0 and no entries, not −ENOENT.

Related issues 3 (0 open — 3 closed)

Actions

#1

Updated by Adam Emerson over 3 years ago

Fixed: https://github.com/ceph/ceph/pull/38977

Actions

#2

Updated by Casey Bodley over 3 years ago

Pull request ID set to 38977

Actions

#3

Updated by Adam Emerson over 3 years ago

Backport set to Pacific

Actions

#4

Updated by Adam Emerson over 3 years ago

Copied to Bug #48940: Listing a new, empty omap datalog errors added

Actions

#5

Updated by Casey Bodley over 3 years ago

Has duplicate Bug #48940: Listing a new, empty omap datalog errors added

Actions

#6

Updated by Casey Bodley about 3 years ago

Status changed from Fix Under Review to Pending Backport

Actions

#7

Updated by Nathan Cutler about 3 years ago

Backport changed from Pacific to pacific

ERROR:root:https://tracker.ceph.com/issues/48929 requires backport to unknown release Pacific

Actions

#8

Updated by Backport Bot about 3 years ago

Copied to Backport #49176: pacific: Listing a new, empty omap datalog errors added

Actions

#9

Updated by Loïc Dachary about 3 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

Also available in: Atom PDF