Description of problem (please be detailed as possible and provide log snippests): ODF operator installations are stuck if the worker nodes have the taint "node.ocs.openshift.io/storage=true:NoSchedule" Prior to ODF-4.9, all OCS pods have tolerations by default for "node.ocs.openshift.io/storage=true:NoSchedule" taint. Customer upgrading from 4.8 and having OCS taint on the worker nodes will end up in this issue and the upgrade won't be complete. Version of all relevant components (if applicable): ODF-4.9 OCP-4.9 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Yes, Upgrade and installation will not finish if taints exist Is there any workaround available to the best of your knowledge? Yes, odf-operator and mcg-operator subscription needs to be updated with required toleration 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? If this is a regression, please provide more details to justify this: Yes Steps to Reproduce: 1. Add OCS taint to worker node 2. Install the ODF operator from Operator Hub 3.