Bug 2042417 - [RADOS Stretch cluster] PG's stuck in remapped+peering after deployment of stretch mode
Summary: [RADOS Stretch cluster] PG's stuck in remapped+peering after deployment of st...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RADOS
Version: 5.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 5.2
Assignee: Greg Farnum
QA Contact: Pawan
Akash Raj
URL:
Whiteboard:
Depends On: 2025800
Blocks: 2102272
TreeView+ depends on / blocked
 
Reported: 2022-01-19 13:49 UTC by Greg Farnum
Modified: 2022-08-10 12:46 UTC (History)
20 users (show)

Fixed In Version: ceph-16.2.8-2.el8cp
Doc Type: Bug Fix
Doc Text:
.PGs no longer get incorrectly stuck in `remapped+peering` state in stretch mode Previously, due to a logical error, when operating a cluster in stretch mode, it was possible for some placement groups (PGs) to get permanently stuck in `remapped+peering` state under certain cluster conditions, causing the data to be unavailable until the OSDs were taken offline. With this fix, PGs choose stable OSD sets and they no longer get incorrectly stuck in `remapped+peering` state in stretch mode.
Clone Of: 2025800
Environment:
Last Closed: 2022-08-09 17:37:27 UTC
Embargoed:
gfarnum: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph pull 44664 0 None Merged pacific: osd: PeeringState: fix selection order in calc_replicated_acting_stretch 2022-05-24 20:47:27 UTC
Red Hat Issue Tracker RHCEPH-3001 0 None None None 2022-01-19 13:51:49 UTC
Red Hat Product Errata RHSA-2022:5997 0 None None None 2022-08-09 17:38:03 UTC

Comment 13 errata-xmlrpc 2022-08-09 17:37:27 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 Security, Bug Fix, 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-2022:5997
Note You need to log in before you can comment on or make changes to this bug.