Description of problem:
The ES es-node-master only pod couldn't be started. The elasticsearch-storage is not defined in statefulset/elasticsearch-master-1. 


#oc get events
45m       45m       7         elasticsearch-clientdatamaster-0-2-67556c645b-rpdtt.157953831d11002a   Pod       spec.containers{elasticsearch}   Warning   Unhealthy   kubelet, ip-10-0-144-241.eu-west-2.compute.internal   Readiness probe failed: cat: /opt/app-root/src/init_failures: No such file or directory

17s       4m        23        elasticsearch-master-1.157955cc140a8304   StatefulSet             Warning   FailedCreate   statefulset-controller   create Pod elasticsearch-master-1-0 in StatefulSet elasticsearch-master-1 failed error: Pod "elasticsearch-master-1-0" is invalid: spec.containers[0].volumeMounts[0].name: Not found: "elasticsearch-storage"


Version-Release number of selected component (if applicable):
registry.reg-aws.openshift.com:443/openshift/ose-elasticsearch-operator:v4.0
registry.reg-aws.openshift.com:443/openshift/ose-elasticsearch-operator@sha256:a8db9520060d448fcf75e0d3684194b64c54c8bb7c3770e72948293db3b98c03

How reproducible:
Always

Steps to Reproduce:
1. Add ES master only nodeSpec in CRD Elalasticsearch
  nodes:
  - nodeCount: 2
    nodeSpec:
      resources: {}
    roles:
    - client
    - data
    - master
    storage: {}
  - nodeCount: 1
    nodeSpec:
      resources: {}
    roles:
    - master
    storage: {}
  redundancyPolicy: SingleRedundancy
2. Check the ES pod and Event
  #oc get statefulset
  #oc get pods --selector es-node-master=true,es-node-data=false
  #oc get event

Actual results:

The pod can be started for elasticsearch-storage is not defined in statefulset

Expected results:
The pod can be started.
If we remove the persistent volume from elasticsearch, 


Additional info: