Description of problem (please be detailed as possible and provide log snippests): If we create a pool via ODF GUI it causes overlapping roots in existing CRSUH map. ----------- 2023-12-04T00:06:59.266113040Z debug 2023-12-04T00:06:59.265+0000 7faca76a9700 0 [pg_autoscaler ERROR root] pool 12 has overlapping roots: {-1, -2} -------- Version of all relevant components (if applicable): 4.13 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? - Due to this CRUSH roots overlap the autoscale stops functioning, will be raising a separate bug/RFE for the same. Is there any workaround available to the best of your knowledge? - We need to modify the CRUSH map. Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Yes. Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: Steps to Reproduce: 1: Deploy an ODF cluster 2: Create a new pool via GUI Actual results: - Adding new pool to cluster causing crush root overlap. Expected results: - Adding new pool to cluster shouldn't cause crush root overlap. Additional info: