[BUG]: Operator e2e scenario for powerscale driver with second set of alternate values is failing in OpenShift cluster

[gilltaran]

Bug Description

In OCP clusters, the master nodes have the taint - key: "node-role.kubernetes.io/master" and not - key: "node-role.kubernetes.io/control-plane" so the controller pods are looking for a taint that doesn't exist in the E2E test scenarios that uses existing alternate values file. The toleration - key: "node-role.kubernetes.io/master" should be added.

Logs

In OCP clusters, the master nodes have the taint - key: "node-role.kubernetes.io/master" and not - key: "node-role.kubernetes.io/control-plane" so the controller pods are looking for a taint that doesn't exist in the E2E test scenarios that uses existing alternate values file. The toleration - key: "node-role.kubernetes.io/master" should be added.

Screenshots

No response

Additional Environment Information

No response

Steps to Reproduce

Execute the specified e2e scenario in OpenShift cluster

Expected Behavior

Controller pods should be successfully scheduled in Openshift cluster

CSM Driver(s)

CSI-Powerscale

Installation Type

No response

Container Storage Modules Enabled

No response

Container Orchestrator

OpenShift Server Version: 4.17

Operating System

RHCOS

[csmbot]

@gilltaran: Thank you for submitting this issue!

The issue is currently awaiting triage. Please make sure you have given us as much context as possible.

If the maintainers determine this is a relevant issue, they will remove the needs-triage label and respond appropriately.

---

We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at [email protected].

[gilltaran]

link: 30361

[gilltaran]

Bug associated with it is resolved and closed hence closing the issue.