Bug 2281729 - [MCG] The prefix filter is ignored in log-based replication policies
Summary: [MCG] The prefix filter is ignored in log-based replication policies
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: Multi-Cloud Object Gateway
Version: 4.16
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.16.0
Assignee: Ben Eli
QA Contact: Sagi Hirshfeld
URL:
Whiteboard:
Depends On:
Blocks: 2260844
TreeView+ depends on / blocked
 
Reported: 2024-05-20 13:04 UTC by Sagi Hirshfeld
Modified: 2024-07-17 13:23 UTC (History)
6 users (show)

Fixed In Version: 4.16.0-118
Doc Type: Enhancement
Doc Text:
The log-based replication optimazation also supports object prefix filtering.
Clone Of:
Environment:
Last Closed: 2024-07-17 13:23:21 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github noobaa noobaa-core pull 8087 0 None Merged Implement support for object prefix filtering in log-based replication optimization 2024-05-30 13:32:18 UTC
Github noobaa noobaa-core pull 8103 0 None Merged [Backport into 5.16] Implement log replication prefix filtering (#8087) 2024-05-30 14:04:33 UTC
Red Hat Product Errata RHSA-2024:4591 0 None None None 2024-07-17 13:23:30 UTC

Comment 5 Sunil Kumar Acharya 2024-06-06 07:34:46 UTC
Please update the RDT flag/text appropriately.

Comment 7 Sagi Hirshfeld 2024-06-11 08:55:08 UTC
Verified the fix on 4.16.0-120.

Exact versions:
---------------
OCP: 4.16.0-0.nightly-2024-06-07-024651
ODF: 4.16.0-120
noobaa core: 5.16.0-1d8127c
noobaa operator: 5.16.0-705652b55ddaabc6bbdf16cb648c4f9a72345cf1
noobaa cli: 5.16.0


Steps taken:
------------
The following steps via OCS-CI automation upload mockup logs to the logs bucket for faster responses:

1. Setup log-based replication with deletion sync between two buckets
2. Patch the policy to sync only a specific prefix
3. Upload objects to two prefixes - one that should be synced and one that shouldn't
4. Wait for the objects under the synced prefix to be replicated
5. Make sure that the objects under the other prefix were not replicated
6. Copy the objects that were not deleted to the same prefix on the target bucket
7. Delete all the objects on both prefixes from the source bucket
8. Wait for the objects with the prefix to be deleted from the target bucket
9. Make sure the objects without the prefix were not deleted from the target bucket

The OCS-CI test in question: https://github.com/sagihirshfeld/ocs-ci/blob/3efc00695446ce85e48d9e416c324569a980f621/tests/functional/object/mcg/test_log_based_bucket_replication.py#L123-L195


Results:
--------
Only the specified prefix was synced, as expected.

Comment 8 Sunil Kumar Acharya 2024-06-18 06:45:26 UTC
Please update the RDT flag/text appropriately.

Comment 10 errata-xmlrpc 2024-07-17 13:23:21 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 (Important: Red Hat OpenShift Data Foundation 4.16.0 security, enhancement & bug fix update), 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/RHSA-2024:4591


Note You need to log in before you can comment on or make changes to this bug.