Description of problem: If an EC pool is created with a name of an already deleted EC pool, the crush map will not get updated for the new EC pool, instead will hold the previous crush rule. The user might have to check the crush maps every time before creating any EC pool just to ensure that a similar pool name had not been created with a crush rule different from the new one. Version-Release number of selected component (if applicable): latest 6.1 How reproducible: always Steps to Reproduce: 1. Create an EC pool 'ecpool' with a specific K+M EC profile. 2. Edit the crush map to meet the specific K+M value requirements. 3. Now delete the pool and create a pool with the same name 'ecpool' Actual results: Crushmap is not updated to reflect the new ecpool Expected results: crushmap should be updated to reflect the new ecpool Additional info: