Actions
Bug #20190
closed"datalog trim" can't work as expected
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.
Updated by Casey Bodley almost 7 years ago
- Status changed from New to Fix Under Review
- Backport set to jewel kraken
Updated by Yehuda Sadeh almost 7 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler almost 7 years ago
- Copied to Backport #20262: jewel: "datalog trim" can't work as expected added
Updated by Nathan Cutler almost 7 years ago
- Copied to Backport #20263: kraken: "datalog trim" can't work as expected added
Updated by Nathan Cutler over 6 years ago
- Status changed from Pending Backport to Resolved
Actions