Project

General

Profile

Actions
Copy link

Bug #20190

closed

"datalog trim" can't work as expected

Added by zhang sw almost 7 years ago. Updated over 6 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 2 (0 open — 2 closed)

Copied to rgw - Backport #20262: jewel: "datalog trim" can't work as expected ResolvedNathan CutlerActions
Copied to rgw - Backport #20263: kraken: "datalog trim" can't work as expected ResolvedNathan CutlerActions
Actions
Copy link
 #2

Updated by Casey Bodley almost 7 years ago

  • Status changed from New to Fix Under Review
  • Backport set to jewel kraken
Actions
Copy link
 #3

Updated by Yehuda Sadeh almost 7 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #4

Updated by Nathan Cutler almost 7 years ago

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

Updated by Nathan Cutler almost 7 years ago

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

Updated by Nathan Cutler over 6 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF