Description of problem (please be detailed as possible and provide log
snippests):
When running deployment ODF 4.13 using AWS, deployment failed with ocs-storagecluster id not in Ready state.

ocs_ci.ocs.exceptions.ResourceWrongStatusException: Resource Resource: ocs-storagecluster is not in expected phase: Ready

From the pod status, noobaa-endpoint is in Pending state:

noobaa-core-0                                                     1/1     Running     0          125m
noobaa-db-pg-0                                                    1/1     Running     0          125m
noobaa-endpoint-6dc5f95c8f-58djq                                  0/1     Pending     0          123m
noobaa-operator-84d8bd8985-lvnrd                                  1/1     Running     0          132m

Deployment config yaml: conf/ocsci/aws_ipi.yaml

DEPLOYMENT:
  allow_lower_instance_requirements: true
ENV_DATA:
  platform: 'aws'
  deployment_type: 'ipi'
  region: 'us-east-2'
  worker_instance_type: 'm4.xlarge'

Console logs: https://ocs4-jenkins-csb-odf-qe.apps.ocp-c1.prod.psi.redhat.com/job/qe-deploy-ocs-cluster/21600/consoleFull 

Version of all relevant components (if applicable):
4.13.0

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?




Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?


Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
N/A

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


Steps to Reproduce:
1. Using Jenkins to deploy AWS cluster 
2. Choose version ODF 4.13 and aws_ipi.yaml



Actual results:
Failed deployment with ocs-storagecluster is not in expected phase: Ready

Expected results:
Cluster should deploy successfully

Additional info: