Bug 1688330
| Summary: | Request for backport for fixed issue https://tracker.ceph.com/issues/21533 | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Scoots Hamilton <schamilt> |
| Component: | RGW | Assignee: | Matt Benjamin (redhat) <mbenjamin> |
| Status: | CLOSED ERRATA | QA Contact: | ceph-qe-bugs <ceph-qe-bugs> |
| Severity: | medium | Docs Contact: | John Brier <jbrier> |
| Priority: | low | ||
| Version: | 3.2 | CC: | agunn, anharris, cbodley, ceph-eng-bugs, jbrier, kbader, mbenjamin, roemerso, sweil, tchandra, tserlin |
| Target Milestone: | z2 | ||
| Target Release: | 3.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-12.2.8-113.el7cp Ubuntu: ceph_12.2.8-96redhat1xenial | Doc Type: | Bug Fix |
| Doc Text: |
.Expiration time is calculated the same as S3
Previously, a Ceph Object Gateway computed relative object's life cycle expiration rules from the time of creation, rather than rounded to midnight UTC as in AWS. This could cause the following error: `botocore.exceptions.ClientError: An error occurred (InvalidArgument) when calling the PutBucketLifecycleConfiguration operation: 'Date' must be at midnight GMT`. Expiration is now rounded to midnight UTC for greater AWS compatibility.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-04-30 15:57:07 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: | 1629656 | ||
|
Comment 7
errata-xmlrpc
2019-04-30 15:57:07 UTC
|