Pod fails to start

Check the value of the pfs_configuration.elasticsearch.privileged property in your custom resource configuration. If it's set to true, run the oc describe pod icp4adeploy-ibm-pfs-elasticsearch-0 command to check the SecurityContextConstraint of the icp4adeploy-ibm-pfs-elasticsearch-0 Pod. Also, ensure it’s set as openshift.io/scc=pfs-privileged-scc.

# oc describe pod icp4adeploy-ibm-pfs-elasticsearch-0
Name:               icp4adeploy-ibm-pfs-elasticsearch-0
Namespace:          icp4adeploy-project
Priority:           0
PriorityClassName:  <none>
Node:               rhel76/<OPENSHIFT_MASTER_IP>
Start Time:         Thu, 21 Nov 2019 18:10:11 +0800
Labels:             app.kubernetes.io/component=pfs-elasticsearch
                    app.kubernetes.io/instance=icp4adeploy
                    app.kubernetes.io/managed-by=Operator
                    app.kubernetes.io/name=icp4adeploy-ibm-pfs-elasticsearch
                    app.kubernetes.io/version=19.0.3
                    controller-revision-hash=icp4adeploy-ibm-pfs-elasticsearch-8675f484d
                    role=elasticsearch
                    statefulset.kubernetes.io/pod-name=icp4adeploy-ibm-pfs-elasticsearch-0
Annotations:        checksum/config=6a3747ddc8ce13afdfc85b6793b847d035e8edd5
                    openshift.io/scc=pfs-privileged-scc
                    productID=5737-I23
                    productName=IBM Cloud Pak for Business Automation
                    productVersion=19.0.3
Status:             Running