Bug 1731486
| Summary: | Applying different expiration lifecycle rules to different objects in same bucket, results show same rule applied to all objects | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Bob Emerson <roemerso> |
| Component: | RGW | Assignee: | Matt Benjamin (redhat) <mbenjamin> |
| Status: | CLOSED ERRATA | QA Contact: | Tejas <tchandra> |
| Severity: | medium | Docs Contact: | Aron Gunn <agunn> |
| Priority: | medium | ||
| Version: | 3.2 | CC: | agunn, assingh, cbodley, ceph-eng-bugs, ceph-qe-bugs, kbader, mbenjamin, sweil, tserlin |
| Target Milestone: | z1 | ||
| Target Release: | 3.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-12.2.12-64.el7cp Ubuntu: ceph_12.2.12-57redhat1 | Doc Type: | Bug Fix |
| Doc Text: |
.Different life-cycle rules for different objects no longer display the same rule applied to all objects
The S3 life-cycle expiration tags are a key-value pair, such that a valid match must match both the key and the value. However, the Ceph Object Gateway only matched the key when computing the `x-amz-expiration` headers, causing tag rules with a common key, but different values, to match incorrectly. With this release, the key and value are both checked when matching a tag rules in the expiration header computation. As a result, objects are displayed with the correct tag rules.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-22 13:29:03 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1726135 | ||
|
Comment 6
Giridhar Ramaraju
2019-08-05 13:10:24 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri 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:3173 |