Please backport and merge the fix to ODF-4.10 stream and update the RDT flag/text appropriately.
Tested versions: ----------------- ODF - quay.io/rhceph-dev/ocs-registry:4.10.9-7 OCP - 4.10.0-0.nightly-2022-12-06-230458 Teststeps: 1. Deploy MCG standalone 2. Taint the nodes oc adm taint nodes compute-0 compute-1 compute-2 xyz=true:NoSchedule 3. Apply tolerations in storage CR and 4 subscriptions 4. Observe if pods are respining automatically and coming to running state 5. For the pods which come to running state check the pods yaml to ensure it has tolerations 6. Respin all the pods to just check if the toleration exists Observation: ------------- 1. Noobaa-default-backing-store pods not getting automatically respinned after updating the storage cluster and subs with the required toleration. However force restart of pod works fine. AFter force restart noobaa-default-backing store pod comes up with the desired toleration We already have a BZ for the above observation : https://bugzilla.redhat.com/show_bug.cgi?id=2149872 ** Content added to storagecluster spec: placement: noobaa-standalone: tolerations: - effect: NoSchedule key: xyz operator: Equal value: "true" - effect: NoSchedule key: node.ocs.openshift.io/storage operator: Equal value: "true" *** Content added to all 4 subs config: tolerations: - effect: NoSchedule key: xyz operator: Equal value: "true" Moving the BZ to verified state
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 (Red Hat OpenShift Data Foundation 4.10.9 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/RHBA-2022:8934