Bug 2099193

Summary: (RHCS 6.0) [RADOS]: Getting New PG number when autoscale is off
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: skanta
Component: RADOSAssignee: Prashant Dhange <pdhange>
Status: CLOSED ERRATA QA Contact: skanta
Severity: high Docs Contact: Eliska <ekristov>
Priority: unspecified    
Version: 5.2CC: akupczyk, amathuri, bhubbard, ceph-eng-bugs, cephqe-warriors, choffman, ekristov, ksirivad, lflores, nojha, pdhange, rfriedma, rzarzyns, sseshasa, tserlin, vumrao
Target Milestone: ---   
Target Release: 6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-17.2.5-17.el9cp Doc Type: Bug Fix
Doc Text:
.The `autoscale-status` command no longer displays the `NEW PG_NUM` value if PG-autoscaling is disabled Previously, the `autoscale-status` command would show the `NEW PG_NUM` value even though PG-autoscaling was not enabled. This would mislead the end user by suggesting that PG autoscaler applied `NEW PG_NUM` value to the pool, which was not the case. With this fix, if the `noautoscale` flag is set, the `NEW PG_NUM` value is not shown in the `autoscale-status` command output.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2023-03-20 18:56:39 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:
Bug Depends On:    
Bug Blocks: 2126050    

Comment 32 errata-xmlrpc 2023-03-20 18:56:39 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.0 Bug Fix 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/RHBA-2023:1360