Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2419667

Summary: Fast EC OSD key-not-found exception on truncate
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Alex Ainscow <aainscow>
Component: RADOSAssignee: Alex Ainscow <aainscow>
Status: CLOSED ERRATA QA Contact: Pawan <pdhiran>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 9.0CC: bhubbard, ceph-eng-bugs, cephqe-warriors, ngangadh, nojha, pdhiran, rzarzyns, tserlin, vereddy, vumrao
Target Milestone: ---   
Target Release: 9.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: ceph-20.1.0-125 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-01-29 07:04:28 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:

Description Alex Ainscow 2025-12-06 11:08:00 UTC 
Description of problem:
An object truncate to an exact shard size will cause a key-not-found exception


Version-Release number of selected component (if applicable):
9.2 of OSD (affects all 9 releases - bug is in tentacle)


How reproducible:
Easily


Steps to Reproduce:
1. Start cluster with fast EC
2. Create a 2+1 EC, 4k chunk size
3. Create a 12k object
4. Truncate to 8k

Any truncate to a N * K * chunk_size where N is any integer will cause issue. 

Actual results:
key-not-found exception


Expected results:
A truncate. 


Additional info:
Seen in field on a tentacle release
Comment 9 errata-xmlrpc 2026-01-29 07:04:28 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 (Moderate: Red Hat Ceph Storage 9.0 Security and Enhancement 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-2026:1536