Project

General

Profile

Bug #48929

Listing a new, empty omap datalog errors

Added by Adam Emerson about 2 years ago. Updated almost 2 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

Duplicated by rgw - Bug #48940: Listing a new, empty omap datalog errors Duplicate
Copied to rgw - Bug #48940: Listing a new, empty omap datalog errors Duplicate
Copied to rgw - Backport #49176: pacific: Listing a new, empty omap datalog errors Resolved

History

#2 Updated by Casey Bodley about 2 years ago

  • Pull request ID set to 38977

#3 Updated by Adam Emerson about 2 years ago

  • Backport set to Pacific

#4 Updated by Adam Emerson about 2 years ago

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

#5 Updated by Casey Bodley about 2 years ago

  • Duplicated by Bug #48940: Listing a new, empty omap datalog errors added

#6 Updated by Casey Bodley about 2 years ago

  • Status changed from Fix Under Review to Pending Backport

#7 Updated by Nathan Cutler almost 2 years ago

  • Backport changed from Pacific to pacific

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

#8 Updated by Backport Bot almost 2 years ago

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

#9 Updated by Loïc Dachary almost 2 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".

Also available in: Atom PDF