Bug 1423858
Summary: | Manifest file of a static large object does not sync in multisite env | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | shilpa <smanjara> |
Component: | RGW | Assignee: | Casey Bodley <cbodley> |
Status: | CLOSED ERRATA | QA Contact: | shilpa <smanjara> |
Severity: | medium | Docs Contact: | Erin Donnelly <edonnell> |
Priority: | unspecified | ||
Version: | 2.2 | CC: | cbodley, ceph-eng-bugs, edonnell, hnallurv, kbader, kdreyer, mbenjamin, owasserm, smanjara, sweil, uboppana |
Target Milestone: | rc | ||
Target Release: | 2.3 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | RHEL: ceph-10.2.7-11.el7cp Ubuntu: ceph_10.2.7-12redhat1xenial | Doc Type: | Bug Fix |
Doc Text: |
.Swift SLOs can now be read from any other zones
Previously, the Ceph Object Gateway failed to fetch manifest files of Swift Static Large Objects (SLO). As a consequence, an attempt to read those objects from any other zone than the zone where the object was originally uploaded failed. This bug has been fixed, and the objects are read from all zones as expected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-06-19 13:29:32 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: | 1412948, 1437916 |
Description
shilpa
2017-02-17 15:01:11 UTC
@Uday, I am re-targeting this to 2.2 for now. Could you please let us know your decision on this BZ? The jewel backport was not completed upstream (http://tracker.ceph.com/issues/19474) so I take it we need patches downstream here? Thanks Ken, I did the manual backport for Jewel at https://github.com/ceph/ceph/pull/14752, and cherry-picked the commits to ceph-2-rhel-patches. Tested again on a new system. Works fine. Moving to verified 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-2017:1497 |