Description of problem (please be detailed as possible and provide log snippests): We are running a cluster with many custom taints, which break ODF pods placement, and we found the article here: https://access.redhat.com/articles/6408481, on how to add tolerance to all the resources, to allow ODF pods to run normally on the nodes with the costume taints. This application is problematic and requires a fix, we want one centralized place to manage the ODF settings and not poke around in countless places to make it work. 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)? Yes. Is there any workaround available to the best of your knowledge? We had to write automation to make sure all the config in sync. Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 - Simple Can this issue reproducible? Simple add a taint to a node, and watch how ceph become degraded. Can this issue reproduce from the UI? Yes. Expected results: We would like to have a single place to config and mange the tolerance. and have all the dependencies to inherent from it.
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 OpenShift Data Foundation 4.16.0 security, enhancement & 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-2024:4591