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 2293908

Summary:	[Backport-6.x] -Recovery started even though the norecover flag is raised in the stretch cluster
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	skanta
Component:	RADOS	Assignee:	Aishwarya Mathuria <amathuri>
Status:	CLOSED ERRATA	QA Contact:	Pawan <pdhiran>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	bhubbard, ceph-eng-bugs, cephqe-warriors, jcaratza, ngangadh, nojha, rpollack, rzarzyns, tserlin, vumrao
Target Milestone:	---
Target Release:	6.1z7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ceph-17.2.6-240	Doc Type:	Bug Fix
Doc Text:	Previously, the autoscaler would run while the `norecover` flag was set leading to creation of new placement groups (PGs) and these PGs requiring to be backfilled. Running of autoscaler while the `norecover` flag is set allowed in cases where I/O is blocked on missing or degraded objects to avoid client I/O hanging indefinitely. With this fix, the autoscaler does not run while the `norecover` flag is set.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-08-28 17:58:15 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 skanta 2024-06-24 09:49:51 UTC

Description of problem:

  +++ This bug was initially created as a clone of Bug #2134786 +++

Please include the fix in Quincy also.

Comment 9 errata-xmlrpc 2024-08-28 17:58:15 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 (Red Hat Ceph Storage 6.1 security, bug fix, and enhancement updates.), 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-2024:5960