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 1595283

Summary:	[Backport] osd: eternal stuck PG in 'unfound_recovery' http://tracker.ceph.com/issues/24373
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Mike Hackett <mhackett>
Component:	RADOS	Assignee:	Josh Durgin <jdurgin>
Status:	CLOSED ERRATA	QA Contact:	Vasishta <vashastr>
Severity:	high	Docs Contact:
Priority:	high
Version:	2.5	CC:	ceph-eng-bugs, ceph-qe-bugs, dzafman, edonnell, jdurgin, kchai, mamccoma, tchandra, tserlin, vumrao
Target Milestone:	z2
Target Release:	2.5
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	RHEL: ceph-10.2.10-37.el7cp Ubuntu: ceph_10.2.10-32redhat1	Doc Type:	Bug Fix
Doc Text:	Under some circumstances placement groups (PGs) could become stuck in the "recovery_unfound" state when a copy of the data was available after an OSD was marked down and then up. To fix this issue, OSDs reset peering when they are marked down and then up, and PGs no longer get stuck in the "recovery_unfound" state.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-05 19:39: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:

Description Mike Hackett 2018-06-26 13:34:07 UTC

Description of problem:\
Request to back port http://tracker.ceph.com/issues/24373 to Jewel (RHCS 2.5).

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

PR: https://github.com/ceph/ceph/pull/22456

Comment 14 Vasishta 2018-08-30 07:43:32 UTC

Hi,

Followed steps mentioned in description of http://tracker.ceph.com/issues/24373

Observed that PGs weren't stuck in unfound_recovery and working fine. Moving to VERIFIED state.

Regards,
Vasishta shastry
QE, Ceph

Comment 16 errata-xmlrpc 2018-09-05 19:39:32 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/RHBA-2018:2651