.`crush_rule` for existing pools can be updated
Previously, the `crush_rule` value for a specific pool was set during the creation of the pool and it was not possible to update later. With this release, `crush_rule` value can be updated for an existing pool.
Created attachment 1697513[details]
ceph_ansible directory
Description of problem:
When attempting to update the Ceph cluster's crush map with Ceph ansible with TripleO the crush map is not updated to the required result. The crush map stays the same as it was prior to the Ceph Ansible run.
Version-Release number of selected component (if applicable):
ceph-ansible-4.0.23-1.el8cp.noarch
How reproducible:
100% (tried twice)
Steps to Reproduce:
1. Deploy an overcloud with the parameters shows in the internal.yaml file attached.
2. update the overcloud using the internal-new.yaml file
OR
1. Deploy a ceph cluster with the class devices as shown in the attache ceph ansible directory
2. run ceph ansible again and adding the crush map
Actual results:
The crush map is not effected by the required changes
Expected results:
A new crush map has been created for the cluster
Additional info:
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 (Important: Red Hat Ceph Storage 4.2 Security and 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/RHSA-2021:0081
Comment 22Red Hat Bugzilla
2023-09-15 00:32:47 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days
Created attachment 1697513 [details] ceph_ansible directory Description of problem: When attempting to update the Ceph cluster's crush map with Ceph ansible with TripleO the crush map is not updated to the required result. The crush map stays the same as it was prior to the Ceph Ansible run. Version-Release number of selected component (if applicable): ceph-ansible-4.0.23-1.el8cp.noarch How reproducible: 100% (tried twice) Steps to Reproduce: 1. Deploy an overcloud with the parameters shows in the internal.yaml file attached. 2. update the overcloud using the internal-new.yaml file OR 1. Deploy a ceph cluster with the class devices as shown in the attache ceph ansible directory 2. run ceph ansible again and adding the crush map Actual results: The crush map is not effected by the required changes Expected results: A new crush map has been created for the cluster Additional info: