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

[ashleyvjoy]

Bug Description

Failing scenario:
scenario: "Install PowerFlex Driver with second set of alternate values"
test file: "testfiles/storage_csm_powerflex_alt_vals_2.yaml"

NAME                                    READY   STATUS    RESTARTS   AGE
powerflex-controller-65cb9fdf84-nvg5x   0/5     Pending   0          7m55s
powerflex-node-4d55w                    2/2     Running   0          7m55s
powerflex-node-pwrpg                    2/2     Running   0          7m55s

Logs

Events:
Type Reason Age From Message

---

Warning FailedScheduling 8m2s default-scheduler 0/5 nodes are available: 2 node(s) didn't match Pod's node affinity/selector, 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }. preemption: 0/5 nodes are available: 5 Preemption is not helpful for scheduling.
Warning FailedScheduling 2m41s default-scheduler 0/5 nodes are available: 2 node(s) didn't match Pod's node affinity/selector, 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }. preemption: 0/5 nodes are available: 5 Preemption is not helpful for scheduling.

Screenshots

NA

Additional Environment Information

NA

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-PowerFelx

Installation Type

No response

Container Storage Modules Enabled

PowerFlex

Container Orchestrator

OpenShift Server Version: 4.17

Operating System

RHCOS

[ashleyvjoy]

link: 30363

[prablr79]

/sync