Bug 1664897 - rgw-multisite: bilog entries not getting trimmed in both sites
Summary: rgw-multisite: bilog entries not getting trimmed in both sites
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW-Multisite
Version: 3.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: z1
: 3.2
Assignee: Casey Bodley
QA Contact: Tejas
URL:
Whiteboard:
: 1657402 (view as bug list)
Depends On:
Blocks: 1690932
TreeView+ depends on / blocked
 
Reported: 2019-01-10 00:22 UTC by Vikhyat Umrao
Modified: 2022-03-13 17:04 UTC (History)
7 users (show)

Fixed In Version: RHEL: ceph-12.2.8-84.el7cp Ubuntu: ceph_12.2.8-70redhat1xenial
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1690932 (view as bug list)
Environment:
Last Closed: 2019-03-07 15:51:27 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-3761 0 None None None 2022-03-13 17:04:14 UTC
Red Hat Knowledge Base (Solution) 4079461 0 Troubleshoot None Ceph - RGW Multisite - bucket index logs(bilogs) not getting trimmed, why? 2019-04-22 20:01:56 UTC
Red Hat Product Errata RHBA-2019:0475 0 None None None 2019-03-07 15:51:36 UTC

Description Vikhyat Umrao 2019-01-10 00:22:15 UTC 
Description of problem:
rgw-multisite: bilog entries not getting trimmed in both sites


Version-Release number of selected component (if applicable):
RHCS 3.1 - 12.2.5-42.el7cp


How reproducible:
Always at the customer site
Comment 20 Vikhyat Umrao 2019-01-21 20:07:10 UTC 
*** Bug 1657402 has been marked as a duplicate of this bug. ***
Comment 54 errata-xmlrpc 2019-03-07 15:51:27 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0475
Note You need to log in before you can comment on or make changes to this bug.