Cause: The etcd deployed with Ansible Service Broker requires a PV be available. Consequence: If no PV is available, etcd will wait until the PV can be satisfied. The Ansible Service Broker application will enter a CrashLoop until etcd is up. Workaround (if any): Before running the installer, set up an NFS host and add the following variables to your hosts file: openshift_hosted_etcd_storage_kind=nfs openshift_hosted_etcd_storage_nfs_options="*(rw,root_squash,sync,no_wdelay)" openshift_hosted_etcd_storage_host=<nfs host> openshift_hosted_etcd_storage_nfs_directory=/path/to/export openshift_hosted_etcd_storage_volume_name=etcd*NOTE[see below] openshift_hosted_etcd_storage_access_modes=['ReadWriteOnce'] openshift_hosted_etcd_storage_volume_size: 1G openshift_hosted_etcd_storage_labels={'storage': 'etcd'} *NOTE If https://bugzilla.redhat.com/show_bug.cgi?id=1467574 is still open, the etcd directory must already exist in the share, it will not be created automatically. If these variables are set and correct, a persistent volume will be created and attached to the broker's etcd instance. Result: etcd will come up once it's PVC is satisfied. Ansible Service Broker will come up when etcd is up.