AFAIK ocs-op deploys the toolbox so change component.
This is valid, but since there will likely be worker nodes without the OCS taint on them in the cluster, this is not a blocker. Moving to OCS 4.6
Still not a blocker, and we're right up against devel freeze. Moving again to OCS 4.7.
PR created : https://github.com/openshift/ocs-operator/pull/815 ocs-metrics-exporter pod will also not run if there are no untainted nodes. Should I go ahead and add a toleration for that as well?
Moving this to MODIFIED as the upstream PR has been merged into the master branch.
Do we need this in 4.6?
(In reply to Mudit Agarwal from comment #7) > Do we need this in 4.6? I don't think so - IMO it is not really critical.
Versions Tested: ----------------- OCP : 4.7.0-0.nightly-2021-02-02-033055 OCS : ocs-operator.v4.7.0-241.ci Steps to verify: ----------------- 1. Toolbox yaml has the toleration added tolerations: - effect: NoSchedule key: node.ocs.openshift.io/storage operator: Equal value: "true" 2. Respin toolbox pod and see if it comes up on tainted node The tests passed, 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 (Moderate: Red Hat OpenShift Container Storage 4.7.0 security, bug fix, and enhancement 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:2041
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days