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 2357061

Summary: [8.1] [Reads Balancer] PGs not getting scaled down post removal of bulk flag on the cluster
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Laura Flores <lflores>
Component: RADOSAssignee: Laura Flores <lflores>
Status: CLOSED UPSTREAM QA Contact: skanta
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.1CC: bhubbard, ceph-eng-bugs, cephqe-warriors, lflores, ngangadh, nojha, pdhiran, rpollack, rzarzyns, skanta, vereddy, vumrao, yhatuka
Target Milestone: ---   
Target Release: 8.1z6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
.Placement groups are not scaled down in `upmap-read` and `read` balancer modes Currently, `pg-upmap-primary` entries are not properly removed for placement groups (PGs) that are pending merge. For example, when the bulk flag is removed on a pool, or any case where the number of PGs in a pool decreases. As a result, the PG scale-down process gets stuck and the number of PGs in the affected pool do not decrease as expected. As a workaround, remove the `pg_upmap_primary` entries in the OSD map of the affected pool. To view the entries, run the `ceph osd dump` command and then run `ceph osd rm-pg-upmap-primary PG_ID` for reach PG in the affected pool. After using the workaround, the PG scale-down process resumes as expected.
Story Points: ---
Clone Of: 2302230 Environment:
Last Closed: 2026-03-04 08:57:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2302230    
Bug Blocks: 2317218    

Description Laura Flores 2025-04-02 23:42:56 UTC
+++ This bug was initially created as a clone of Bug #2302230 +++

Comment 11 Red Hat Bugzilla 2026-03-04 08:57:00 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.