Bug 1258618
| Summary: | rgw: COPYing an old object onto itself produces a truncated object | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Yehuda Sadeh <yehuda> |
| Component: | RGW | Assignee: | Yehuda Sadeh <yehuda> |
| Status: | CLOSED ERRATA | QA Contact: | ceph-qe-bugs <ceph-qe-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.3.0 | CC: | cbodley, ceph-eng-bugs, ceph-qe-bugs, flucifre, kbader, kdreyer, mbenjamin, owasserm, smanjara, sweil, vakulkar |
| Target Milestone: | rc | ||
| Target Release: | 1.3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-0.94.2-9.el7cp | Doc Type: | Bug Fix |
| Doc Text: |
Under certain circumstances, copying an object onto itself (for example,
to change its metadata) produced a truncated object. The truncated object
had correct metadata, including the original size, but the underlying RADOS
object was smaller. Consequently, when a client attempted to fetch the
object, it received less data than indicated by the Content-Length header,
blocked for more, and eventually timed out. This bug has been fixed, and
the object can now be read successfully in the aforementioned scenario.
|
Story Points: | --- |
| Clone Of: | 1258617 | Environment: | |
| Last Closed: | 2015-11-23 20:22:20 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: | |||
|
Comment 8
shilpa
2015-11-06 07:01:45 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/RHSA-2015:2512 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/RHSA-2015:2066 |