Bug 2293908 - [Backport-6.x] -Recovery started even though the norecover flag is raised in the stretch cluster
Summary: [Backport-6.x] -Recovery started even though the norecover flag is raised in ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 6.1z7
Assignee: Aishwarya Mathuria
QA Contact: Pawan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-06-24 09:49 UTC by skanta
Modified: 2024-08-28 17:58 UTC (History)
10 users (show)

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.
Clone Of:
Environment:
Last Closed: 2024-08-28 17:58:15 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph pull 57568 0 None open quincy: mgr/pg_autoscaler: add check for norecover flag 2024-07-10 18:25:00 UTC
Red Hat Issue Tracker RHCEPH-9215 0 None None None 2024-06-24 09:50:28 UTC
Red Hat Product Errata RHBA-2024:5960 0 None None None 2024-08-28 17:58:19 UTC

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
Note You need to log in before you can comment on or make changes to this bug.