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 1191597

Summary: Lost object due to OSD failure on one node
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Tupper Cole <tcole>
Component: DistributionAssignee: ceph-eng-bugs <ceph-eng-bugs>
Status: CLOSED WONTFIX QA Contact: ceph-qe-bugs <ceph-qe-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 1.2.2CC: bhubbard, flucifre, nlevine, sjust
Target Milestone: pre-dev-freeze   
Target Release: 1.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-13 20:45:49 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:
Attachments:
Description Flags
Lost object and pg details none

Description Tupper Cole 2015-02-11 14:55:22 UTC
Created attachment 990474 [details]
Lost object and pg details

Description of problem:
During an event in which four OSDs misbehaved, an object seems to have been lost. All other OSDs on which the pg has been on are still available. 

Version-Release number of selected component (if applicable):
0.80.7

How reproducible:
N/A

Steps to Reproduce:
1.
2.
3.

Actual results:



Expected results:


Additional info:
Attached are the output of `ceph health detail`, ceph pg <id> list_missing, and `ceph pg <id> query`. OSD log from the time has been provided: 

 ceph-post-file: c53bd231-dcb0-4cf0-807b-6f5ff871afde

Comment 1 Brad Hubbard 2015-02-12 00:54:20 UTC
Hi Neil,

I initially set the rhc‑1.3.0 flag for this but wondering if we should add
rhc‑1.2.z?

Comment 2 Neil Levine 2015-02-12 01:12:09 UTC
I've set it to 1.2.4 which will be the next Z-stream point release.
1.2.3 is about to get frozen RSN so if this is a urgent/sev1 bug we can assign it back to that version. 
Need engineering/support to weigh in on urgency.

Comment 4 Samuel Just 2015-04-13 18:59:30 UTC
There is no bug here to fix?  This should probably just be closed.

Comment 5 RHEL Program Management 2015-04-13 20:45:49 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.