Project

General

Profile

Bug #20190

"datalog trim" can't work as expected

Added by zhang sw over 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
jewel kraken
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The radosgw-admin command datalog trim can't remove the log as expected.
It returns "ERROR: trim_entries(): (61) No data available" even if data logs actually exist.


Related issues

Copied to rgw - Backport #20262: jewel: "datalog trim" can't work as expected Resolved
Copied to rgw - Backport #20263: kraken: "datalog trim" can't work as expected Resolved

History

#2 Updated by Casey Bodley over 5 years ago

  • Status changed from New to Fix Under Review
  • Backport set to jewel kraken

#3 Updated by Yehuda Sadeh over 5 years ago

  • Status changed from Fix Under Review to Pending Backport

#4 Updated by Nathan Cutler over 5 years ago

  • Copied to Backport #20262: jewel: "datalog trim" can't work as expected added

#5 Updated by Nathan Cutler over 5 years ago

  • Copied to Backport #20263: kraken: "datalog trim" can't work as expected added

#6 Updated by Nathan Cutler about 5 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF