While upgrading OCP from 3.6 to 3.7.23 using openshift-ansible 3.7.37, I encountered this error:

TASK [openshift_logging_elasticsearch : set_fact] ******************************
Thursday 15 March 2018  19:04:57 +0000 (0:00:00.621)       0:03:55.458 ******** 
fatal: [204.236.205.127]: FAILED! => {"msg": "The conditional check 'item.status.containerStatuses[1].ready == true' failed. The error was: error while evaluating conditional (item.status.containerStatuses[1].ready == true): list object has no element 1\n\nThe error appears to have been in '/home/opsmedic/aos-cd/git/openshift-tools/openshift/installer/vendored/openshift-ansible-3.7.37/roles/openshift_logging_elasticsearch/tasks/get_es_version.yml': line 9, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- set_fact:\n  ^ here\n"}

PLAY RECAP *********************************************************************
18.232.94.26               : ok=47   changed=5    unreachable=0    failed=0   
204.236.205.127            : ok=105  changed=8    unreachable=0    failed=1   
34.207.102.240             : ok=47   changed=5    unreachable=0    failed=0   
34.227.95.221              : ok=47   changed=5    unreachable=0    failed=0   
34.228.247.65              : ok=47   changed=5    unreachable=0    failed=0   
35.173.181.73              : ok=47   changed=5    unreachable=0    failed=0   
35.174.0.226               : ok=48   changed=6    unreachable=0    failed=0   
52.71.96.22                : ok=47   changed=5    unreachable=0    failed=0   
52.91.74.69                : ok=48   changed=6    unreachable=0    failed=0   
54.152.199.184             : ok=47   changed=5    unreachable=0    failed=0   
localhost                  : ok=11   changed=0    unreachable=0    failed=0   


INSTALLER STATUS ***************************************************************
Initialization             : Complete
Logging Install            : In Progress


Deployment Config
-----------------

apiVersion: v1
kind: DeploymentConfig
metadata:
  creationTimestamp: 2018-03-14T18:02:25Z
  generation: 2
  labels:
    component: es
    deployment: logging-es-data-master-1stfd5d8
    logging-infra: elasticsearch
    provider: openshift
  name: logging-es-data-master-1stfd5d8
  namespace: logging
  resourceVersion: "57277"
  selfLink: /oapi/v1/namespaces/logging/deploymentconfigs/logging-es-data-master-1stfd5d8
  uid: d9f830ac-27b1-11e8-9294-0ede7012d9c6
spec:
  replicas: 1
  selector:
    component: es
    deployment: logging-es-data-master-1stfd5d8
    logging-infra: elasticsearch
    provider: openshift
  strategy:
    activeDeadlineSeconds: 21600
    recreateParams:
      timeoutSeconds: 600
    resources: {}
    type: Recreate
  template:
    metadata:
      creationTimestamp: null
      labels:
        component: es
        deployment: logging-es-data-master-1stfd5d8
        logging-infra: elasticsearch
        provider: openshift
      name: logging-es-data-master-1stfd5d8
    spec:
      containers:
      - env:
        - name: DC_NAME
          value: logging-es-data-master-1stfd5d8
        - name: NAMESPACE
          valueFrom:
            fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
        - name: KUBERNETES_TRUST_CERT
          value: "true"
        - name: SERVICE_DNS
          value: logging-es-cluster
        - name: CLUSTER_NAME
          value: logging-es
        - name: INSTANCE_RAM
          value: 12Gi
        - name: HEAP_DUMP_LOCATION
          value: /elasticsearch/persistent/heapdump.hprof
        - name: NODE_QUORUM
          value: "2"
        - name: RECOVER_EXPECTED_NODES
          value: "3"
        - name: RECOVER_AFTER_TIME
          value: 5m
        - name: READINESS_PROBE_TIMEOUT
          value: "30"
        - name: POD_LABEL
          value: component=es
        - name: IS_MASTER
          value: "true"
        - name: HAS_DATA
          value: "true"
        image: registry.reg-aws.openshift.com:443/openshift3/logging-elasticsearch:v3.6
        imagePullPolicy: IfNotPresent
        name: elasticsearch
        ports:
        - containerPort: 9200
          name: restapi
          protocol: TCP
        - containerPort: 9300
          name: cluster
          protocol: TCP
        readinessProbe:
          exec:
            command:
            - /usr/share/java/elasticsearch/probe/readiness.sh
          failureThreshold: 3
          initialDelaySeconds: 10
          periodSeconds: 5
          successThreshold: 1
          timeoutSeconds: 30
        resources:
          limits:
            memory: 12Gi
          requests:
            cpu: 375m
            memory: 12Gi
        terminationMessagePath: /dev/termination-log
        terminationMessagePolicy: File
        volumeMounts:
        - mountPath: /etc/elasticsearch/secret
          name: elasticsearch
          readOnly: true
        - mountPath: /usr/share/java/elasticsearch/config
          name: elasticsearch-config
          readOnly: true
        - mountPath: /elasticsearch/persistent
          name: elasticsearch-storage
      dnsPolicy: ClusterFirst
      nodeSelector:
        type: infra
      restartPolicy: Always
      schedulerName: default-scheduler
      securityContext:
        supplementalGroups:
        - 65534
      serviceAccount: aggregated-logging-elasticsearch
      serviceAccountName: aggregated-logging-elasticsearch
      terminationGracePeriodSeconds: 30
      volumes:
      - name: elasticsearch
        secret:
          defaultMode: 420
          secretName: logging-elasticsearch
      - configMap:
          defaultMode: 420
          name: logging-elasticsearch
        name: elasticsearch-config
      - name: elasticsearch-storage
        persistentVolumeClaim:
          claimName: logging-es-0
  test: false
  triggers:
  - type: ConfigChange
status:
  availableReplicas: 1
  conditions:
  - lastTransitionTime: 2018-03-14T18:03:54Z
    lastUpdateTime: 2018-03-14T18:03:54Z
    message: replication controller "logging-es-data-master-1stfd5d8-1" successfully
      rolled out
    reason: NewReplicationControllerAvailable
    status: "True"
    type: Progressing
  - lastTransitionTime: 2018-03-14T22:36:42Z
    lastUpdateTime: 2018-03-14T22:36:42Z
    message: Deployment config has minimum availability.
    status: "True"
    type: Available
  details:
    causes:
    - type: ConfigChange
    message: config change
  latestVersion: 1
  observedGeneration: 2
  readyReplicas: 1
  replicas: 1
  unavailableReplicas: 0
  updatedReplicas: 1