Description of problem - Custom toleration is not replicated to ocs-provider-server pod

 

The OCP platform infrastructure and deployment type (AWS, Bare Metal, VMware, etc. Please clarify if it is platform agnostic deployment), (IPI/UPI): VMware(UPI)

 

The version of all relevant components (OCP, ODF, RHCS, ACM whichever is applicable):

OCP: 4.18.0-0.nightly-2024-11-21-131835

ODF: 4.18.0-72

 

Does this issue impact your ability to continue to work with the product?

 

Is there any workaround available to the best of your knowledge?

No

 

Can this issue be reproduced? If so, please provide the hit rate

Yes, 100%

 

Can this issue be reproduced from the UI?

If this is a regression, please provide more details to justify this:

Steps to Reproduce:

1. Apply custom taint to node

2. Apply custom tolerations in storagecluster yaml

`Spec:

  placement:

    all:

      tolerations:

      - effect: NoSchedule

        key: xyz

        operator: Equal

        value: "true"

      - effect: NoSchedule

        key: node.ocs.openshift.io/storage

        operator: Equal

        value: "true"

    csi-plugin:

      tolerations:

      - effect: NoSchedule

        key: xyz

        operator: Equal

        value: "true"

      - effect: NoSchedule

        key: node.ocs.openshift.io/storage

        operator: Equal

        value: "true"

    csi-provisioner:

      tolerations:

      - effect: NoSchedule

        key: xyz

        operator: Equal

        value: "true"

      - effect: NoSchedule

        key: node.ocs.openshift.io/storage

        operator: Equal

        value: "true"

    mds:

      tolerations:

      - effect: NoSchedule

        key: xyz

        operator: Equal

        value: "true"

      - effect: NoSchedule

        key: node.ocs.openshift.io/storage

        operator: Equal

        value: "true"

    noobaa-core:

      tolerations:

      - effect: NoSchedule

        key: xyz

        operator: Equal

        value: "true"

      - effect: NoSchedule

        key: node.ocs.openshift.io/storage

        operator: Equal

        value: "true"

    metrics-exporter:

      tolerations:

      - effect: NoSchedule

        key: xyz

        operator: Equal

        value: "true"

      - effect: NoSchedule

        key: node.ocs.openshift.io/storage

        operator: Equal

        value: "true"

    rgw:

      tolerations:

      - effect: NoSchedule

        key: xyz

        operator: Equal

        value: "true"

      - effect: NoSchedule

        key: node.ocs.openshift.io/storage

        operator: Equal

        value: "true"

    toolbox:

      tolerations:

      - effect: NoSchedule

        key: xyz

        operator: Equal

        value: "true"

      - effect: NoSchedule

        key: node.ocs.openshift.io/storage

        operator: Equal

        value: "true"

`

3. Apply custom tolerations on odf operator 
$ oc -n openshift-storage patch Subscription odf-operator -n openshift-storage -p '{"spec": {"config":  {"tolerations": [

{"effect": "NoSchedule", "key": "xyz", "operator": "Equal", "value": "true"}

]}}}' --type merge

4. Check the tolerations on all pods

The exact date and time when the issue was observed, including timezone details:

 

Actual results:

Tolerations not applied on ocs-provider-server-94b64f85d-9rd4w pod and pod is in pending state

$ oc get pods ocs-provider-server-94b64f85d-9rd4w -n openshift-storage -o yaml | grep tolerations -A 20

  tolerations:

  - effect: NoSchedule

    key: node.ocs.openshift.io/storage

    operator: Equal

    value: "true"

  - effect: NoExecute

    key: node.kubernetes.io/not-ready

    operator: Exists

    tolerationSeconds: 300

  - effect: NoExecute

    key: node.kubernetes.io/unreachable

    operator: Exists

    tolerationSeconds: 300

 

Expected results:

Custom toleration applied to ocs-provider-server-94b64f85d-9rd4w pod

 

Logs collected and log location:

 

Additional info: