Reboot test failure — Elasticsearch

gistfile1.txt

Cluster level logging using Elasticsearch
  should check that logs from pods on all nodes are ingested into Elasticsearch
  /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/es_cluster_logging.go:46
[BeforeEach] Cluster level logging using Elasticsearch
  /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/es_cluster_logging.go:42
>>> testContext.KubeConfig: /Users/maxforbes/.kube/config
[It] should check that logs from pods on all nodes are ingested into Elasticsearch
  /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/es_cluster_logging.go:46
STEP: Checking the Elasticsearch service exists.
STEP: Checking to make sure the Elasticsearch pods are running
INFO: Waiting up to 5m0s for pod elasticsearch-logging-s0cy6 status to be running
STEP: Checking to make sure we are talking to an Elasticsearch service.
STEP: Checking health of Elasticsearch service.
STEP: Waiting for the pods to succeed.
INFO: Waiting up to 5m0s for pod synthlogger-0 status to be success or failure
INFO: No Status.Info for container synth-logger in pod synthlogger-0 yet
INFO: Waiting for pod synthlogger-0 in namespace es-logging-2633 status to be "success or failure" (found "Pending") (44.891343ms)
INFO: Nil State.Termination for container synth-logger in pod synthlogger-0 in namespace es-logging-2633 so far
INFO: Waiting for pod synthlogger-0 in namespace es-logging-2633 status to be "success or failure" (found "Running") (5.088440066s)
INFO: Nil State.Termination for container synth-logger in pod synthlogger-0 in namespace es-logging-2633 so far
INFO: Waiting for pod synthlogger-0 in namespace es-logging-2633 status to be "success or failure" (found "Running") (10.131499553s)
STEP: Saw pod success
INFO: Waiting up to 5m0s for pod synthlogger-1 status to be success or failure
STEP: Saw pod success
STEP: Checking all the log lines were ingested into Elasticsearch
INFO: After 365.781052ms expecting to find 200 log lines but saw only 0
INFO: After 10.414296167s expecting to find 200 log lines but saw only 0
INFO: After 20.464188366s expecting to find 200 log lines but saw only 0
INFO: After 30.512718262s expecting to find 200 log lines but saw only 0
INFO: After 40.563249248s expecting to find 200 log lines but saw only 0
INFO: After 50.61333161s expecting to find 200 log lines but saw only 0
INFO: After 1m0.6629062s expecting to find 200 log lines but saw only 0
INFO: After 1m10.712962319s expecting to find 200 log lines but saw only 0
INFO: After 1m20.760815678s expecting to find 200 log lines but saw only 0
INFO: After 1m30.808696949s expecting to find 200 log lines but saw only 0
INFO: After 1m40.858094152s expecting to find 200 log lines but saw only 0
INFO: After 1m50.90731286s expecting to find 200 log lines but saw only 0
INFO: After 2m0.957368863s expecting to find 200 log lines but saw only 0
INFO: After 2m11.006881649s expecting to find 200 log lines but saw only 0
INFO: After 2m21.054728697s expecting to find 200 log lines but saw only 0
INFO: After 2m31.103414996s expecting to find 200 log lines but saw only 0
INFO: After 2m41.152101916s expecting to find 200 log lines but saw only 0
INFO: After 2m51.200775382s expecting to find 200 log lines but saw only 0
INFO: After 3m1.248547374s expecting to find 200 log lines but saw only 0
INFO: After 3m11.296277834s expecting to find 200 log lines but saw only 0
INFO: After 3m21.347222435s expecting to find 200 log lines but saw only 0
INFO: After 3m31.397938288s expecting to find 200 log lines but saw only 0
INFO: After 3m41.44638457s expecting to find 200 log lines but saw only 0
INFO: After 3m51.499309641s expecting to find 200 log lines but saw only 0
INFO: After 4m1.550525893s expecting to find 200 log lines but saw only 0
INFO: After 4m11.601905469s expecting to find 200 log lines but saw only 0
INFO: After 4m21.651153919s expecting to find 200 log lines but saw only 0
INFO: After 4m31.698742326s expecting to find 200 log lines but saw only 0
INFO: After 4m41.748235855s expecting to find 200 log lines but saw only 0
INFO: After 4m51.801286318s expecting to find 200 log lines but saw only 0
INFO: After 5m1.849907513s expecting to find 200 log lines but saw only 0
INFO: After 5m11.897347555s expecting to find 200 log lines but saw only 0
INFO: After 5m21.951531818s expecting to find 200 log lines but saw only 0
INFO: After 5m32.001290316s expecting to find 200 log lines but saw only 0
INFO: After 5m42.051788977s expecting to find 200 log lines but saw only 0
INFO: After 5m52.100779676s expecting to find 200 log lines but saw only 0
INFO: After 6m2.166453562s expecting to find 200 log lines but saw only 0
INFO: After 6m12.215729355s expecting to find 200 log lines but saw only 0
INFO: After 6m22.265824838s expecting to find 200 log lines but saw only 0
INFO: After 6m32.365369114s expecting to find 200 log lines but saw only 0
INFO: After 6m42.414391969s expecting to find 200 log lines but saw only 0
INFO: After 6m52.463215151s expecting to find 200 log lines but saw only 0
INFO: After 7m2.511581604s expecting to find 200 log lines but saw only 0
INFO: After 7m12.577678528s expecting to find 200 log lines but saw only 0
INFO: After 7m22.626109829s expecting to find 200 log lines but saw only 0
INFO: After 7m32.67282525s expecting to find 200 log lines but saw only 0
INFO: After 7m42.721267778s expecting to find 200 log lines but saw only 0
INFO: After 7m52.769122604s expecting to find 200 log lines but saw only 0
INFO: After 8m2.816151554s expecting to find 200 log lines but saw only 0
INFO: After 8m12.864928589s expecting to find 200 log lines but saw only 0
INFO: After 8m22.911868365s expecting to find 200 log lines but saw only 0
INFO: After 8m32.962643942s expecting to find 200 log lines but saw only 0
INFO: After 8m43.012803183s expecting to find 200 log lines but saw only 0
INFO: After 8m53.061585902s expecting to find 200 log lines but saw only 0
INFO: After 9m3.109987554s expecting to find 200 log lines but saw only 0
INFO: After 9m13.161599622s expecting to find 200 log lines but saw only 0
INFO: After 9m23.208541388s expecting to find 200 log lines but saw only 0
INFO: After 9m33.258275273s expecting to find 200 log lines but saw only 0
INFO: After 9m43.306512326s expecting to find 200 log lines but saw only 0
INFO: After 9m53.355362092s expecting to find 200 log lines but saw only 0

• Failure [649.886 seconds]
Cluster level logging using Elasticsearch
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/es_cluster_logging.go:47
  should check that logs from pods on all nodes are ingested into Elasticsearch [It]
  /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/es_cluster_logging.go:46

  Failed to find all 200 log lines

  /go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/es_cluster_logging.go:337