Description of problem:
When setting openshift_hosted_logging_enable_ops_cluster=true additionally in logging deployment with dynamic pv, installer will fail at TASK [openshift_hosted_logging : Wait for component pods to be running] 

The logging-es deployer pod run into error status due to "Unable to mount volumes for pod "logging-es-puwie4np-4-x3dwz_logging"

Checked related code, found openshift_hosted_logging_ops_pvc_prefix and openshift_hosted_logging_pvc_prefix are both hardcoded with the same value, only one pvc named "logging-es1" created under logging project during installation.


Version-Release number of selected component (if applicable):
openshift-ansible-3.4.29-1.git.0.cdb211b.el7.noarch.rpm

How reproducible:
Always

Steps to Reproduce:
1.Set the following options in ansible inventory file and start installation playbook
openshift_hosted_logging_deploy=true
openshift_hosted_logging_deployer_prefix=x.openshift.com/openshift3/
openshift_hosted_logging_deployer_version=3.4.0
openshift_hosted_logging_storage_kind=dynamic
openshift_hosted_logging_enable_ops_cluster=true


Actual results:
[root@gpei-test-master-etcd-1 ~]# oc get pod
NAME                              READY     STATUS             RESTARTS   AGE
logging-curator-1-ax9ju           0/1       CrashLoopBackOff   34         4h
logging-curator-ops-1-gkqyz       1/1       Running            0          4h
logging-deployer-va6vy            0/1       Completed          0          4h
logging-es-ops-p4ocsboo-1-gdixt   1/1       Running            0          4h
logging-es-puwie4np-1-deploy      0/1       Error              0          4h
logging-kibana-1-lnytb            2/2       Running            0          4h
logging-kibana-ops-1-r8uau        2/2       Running            0          4h

Start new deployment of logging-es-puwie4np
[root@gpei-test-master-etcd-1 ~]# oc describe pod logging-es-puwie4np-4-x3dwz
Name:			logging-es-puwie4np-4-x3dwz
Namespace:		logging
Security Policy:	restricted
Node:			gpei-test-node-registry-router-1/10.240.0.7
Start Time:		Mon, 28 Nov 2016 02:54:55 -0500
Labels:			component=es
			deployment=logging-es-puwie4np-4
			deploymentconfig=logging-es-puwie4np
			provider=openshift
Status:			Pending
IP:			
Controllers:		ReplicationController/logging-es-puwie4np-4
Containers:
  elasticsearch:
    Container ID:	
    Image:		x.openshift.com/openshift3/logging-elasticsearch:3.4.0
    Image ID:		
    Ports:		9200/TCP, 9300/TCP
    Limits:
      memory:	8Gi
    Requests:
      memory:		512Mi
    State:		Waiting
      Reason:		ContainerCreating
    Ready:		False
    Restart Count:	0
    Volume Mounts:
      /elasticsearch/persistent from elasticsearch-storage (rw)
      /etc/elasticsearch/secret from elasticsearch (ro)
      /usr/share/java/elasticsearch/config from elasticsearch-config (ro)
      /var/run/secrets/kubernetes.io/serviceaccount from aggregated-logging-elasticsearch-token-j8fb4 (ro)
    Environment Variables:
      NAMESPACE:		logging (v1:metadata.namespace)
      KUBERNETES_TRUST_CERT:	true
      SERVICE_DNS:		logging-es-cluster
      CLUSTER_NAME:		logging-es
      INSTANCE_RAM:		8G
      NODE_QUORUM:		1
      RECOVER_AFTER_NODES:	0
      RECOVER_EXPECTED_NODES:	1
      RECOVER_AFTER_TIME:	5m
Conditions:
  Type		Status
  Initialized 	True 
  Ready 	False 
  PodScheduled 	True 
Volumes:
  elasticsearch:
    Type:	Secret (a volume populated by a Secret)
    SecretName:	logging-elasticsearch
  elasticsearch-config:
    Type:	ConfigMap (a volume populated by a ConfigMap)
    Name:	logging-elasticsearch
  elasticsearch-storage:
    Type:	PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:	logging-es1
    ReadOnly:	false
  aggregated-logging-elasticsearch-token-j8fb4:
    Type:	Secret (a volume populated by a Secret)
    SecretName:	aggregated-logging-elasticsearch-token-j8fb4
QoS Class:	Burstable
Tolerations:	<none>
Events:
  FirstSeen	LastSeen	Count	From						SubobjectPath	Type		Reason		Message
  ---------	--------	-----	----						-------------	--------	------		-------
  3m		3m		1	{default-scheduler }						Normal		Scheduled	Successfully assigned logging-es-puwie4np-4-x3dwz to gpei-test-node-registry-router-1
  1m		1m		1	{kubelet gpei-test-node-registry-router-1}			Warning		FailedMount	Unable to mount volumes for pod "logging-es-puwie4np-4-x3dwz_logging(f37bee08-b53f-11e6-bd3f-42010af00005)": timeout expired waiting for volumes to attach/mount for pod "logging-es-puwie4np-4-x3dwz"/"logging". list of unattached/unmounted volumes=[elasticsearch-storage]
  1m		1m		1	{kubelet gpei-test-node-registry-router-1}			Warning		FailedSync	Error syncing pod, skipping: timeout expired waiting for volumes to attach/mount for pod "logging-es-puwie4np-4-x3dwz"/"logging". list of unattached/unmounted volumes=[elasticsearch-storage]

[root@gpei-test-master-etcd-1 ~]# oc get pv
NAME                                       CAPACITY   ACCESSMODES   RECLAIMPOLICY   STATUS    CLAIM                 REASON    AGE
pvc-6a64b62c-b517-11e6-8a33-42010af00004   10Gi       RWO           Delete          Bound     logging/logging-es1             4h

[root@gpei-test-master-etcd-1 ~]# oc get pvc
NAME          STATUS    VOLUME                                     CAPACITY   ACCESSMODES   AGE
logging-es1   Bound     pvc-6a64b62c-b517-11e6-8a33-42010af00004   10Gi       RWO           4h

[root@gpei-test-master-etcd-1 ~]# oc describe pvc logging-es1
Name:		logging-es1
Namespace:	logging
StorageClass:	dynamic
Status:		Bound
Volume:		pvc-6a64b62c-b517-11e6-8a33-42010af00004
Labels:		app=logging-pvc-dynamic-template
		component=support
		logging-infra=support
		provider=openshift
Capacity:	10Gi
Access Modes:	RWO
No events.


Expected results:
logging-es and logging-es-ops pod should both have available pv and pods could be running.

Additional info: