ResultFAILURE
Tests 1 failed / 145 succeeded
Started2017-05-04 03:33
Elapsed8m22s
Revision

Test Failures


[k8s.io] Projected should be consumable from pods in volume with mappings as non-root [Conformance] [Volume] 7.54s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Projected\sshould\sbe\sconsumable\sfrom\spods\sin\svolume\swith\smappings\sas\snon\-root\s\[Conformance\]\s\[Volume\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected.go:418
Expected error:
    <*errors.errorString | 0xc420200ee0>: {
        s: "failed to get logs from pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e for projected-configmap-volume-test: an error on the server (\"unknown\") has prevented the request from succeeding (get pods pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e)",
    }
    failed to get logs from pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e for projected-configmap-volume-test: an error on the server ("unknown") has prevented the request from succeeding (get pods pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e)
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2183
				
				Click to see stdout/stderrfrom junit_21.xml

Filter through log files | View test history on testgrid


Show 145 Passed Tests

Show 442 Skipped Tests

Error lines from build-log.txt

... skipping 3196 lines ...
May  4 03:34:32.106: INFO: ForEach: Found 1 pods from the filter.  Now looping through them.
May  4 03:34:32.106: INFO: Running '/usr/local/bin/kubectl --server=https://10.240.0.7:6443 --kubeconfig=/home/ubuntu/.kube/config describe pod redis-master-40qpd --namespace=e2e-tests-kubectl-9mkft'
May  4 03:34:32.252: INFO: stderr: ""
May  4 03:34:32.252: INFO: stdout: "Name:\t\tredis-master-40qpd\nNamespace:\te2e-tests-kubectl-9mkft\nNode:\t\tjuju-f88ba1-2/10.240.0.9\nStart Time:\tThu, 04 May 2017 03:34:25 +0000\nLabels:\t\tapp=redis\n\t\trole=master\nAnnotations:\tkubernetes.io/created-by={\"kind\":\"SerializedReference\",\"apiVersion\":\"v1\",\"reference\":{\"kind\":\"ReplicationController\",\"namespace\":\"e2e-tests-kubectl-9mkft\",\"name\":\"redis-master\",\"uid\":\"92690e6f-307a-11...\nStatus:\t\tRunning\nIP:\t\t10.1.15.30\nControllers:\tReplicationController/redis-master\nContainers:\n  redis-master:\n    Container ID:\tdocker://9a9dfe7335e229157c2dc03ff33de325e15a0608a364ab4f3a2ac3478661d212\n    Image:\t\tgcr.io/google_containers/redis:e2e\n    Image ID:\t\tdocker-pullable://gcr.io/google_containers/redis@sha256:f066bcf26497fbc55b9bf0769cb13a35c0afa2aa42e737cc46b7fb04b23a2f25\n    Port:\t\t6379/TCP\n    State:\t\tRunning\n      Started:\t\tThu, 04 May 2017 03:34:27 +0000\n    Ready:\t\tTrue\n    Restart Count:\t0\n    Environment:\t<none>\n    Mounts:\n      /var/run/secrets/kubernetes.io/serviceaccount from default-token-0dvv2 (ro)\nConditions:\n  Type\t\tStatus\n  Initialized \tTrue \n  Ready \tTrue \n  PodScheduled \tTrue \nVolumes:\n  default-token-0dvv2:\n    Type:\tSecret (a volume populated by a Secret)\n    SecretName:\tdefault-token-0dvv2\n    Optional:\tfalse\nQoS Class:\tBestEffort\nNode-Selectors:\t<none>\nTolerations:\tnode.alpha.kubernetes.io/notReady=:Exists:NoExecute for 300s\n\t\tnode.alpha.kubernetes.io/unreachable=:Exists:NoExecute for 300s\nEvents:\n  FirstSeen\tLastSeen\tCount\tFrom\t\t\tSubObjectPath\t\t\tType\t\tReason\t\tMessage\n  ---------\t--------\t-----\t----\t\t\t-------------\t\t\t--------\t------\t\t-------\n  7s\t\t7s\t\t1\tdefault-scheduler\t\t\t\t\tNormal\t\tScheduled\tSuccessfully assigned redis-master-40qpd to juju-f88ba1-2\n  5s\t\t5s\t\t1\tkubelet, juju-f88ba1-2\tspec.containers{redis-master}\tNormal\t\tPulled\t\tContainer image \"gcr.io/google_containers/redis:e2e\" already present on machine\n  5s\t\t5s\t\t1\tkubelet, juju-f88ba1-2\tspec.containers{redis-master}\tNormal\t\tCreated\t\tCreated container with id 9a9dfe7335e229157c2dc03ff33de325e15a0608a364ab4f3a2ac3478661d212\n  5s\t\t5s\t\t1\tkubelet, juju-f88ba1-2\tspec.containers{redis-master}\tNormal\t\tStarted\t\tStarted container with id 9a9dfe7335e229157c2dc03ff33de325e15a0608a364ab4f3a2ac3478661d212\n"
May  4 03:34:32.252: INFO: Running '/usr/local/bin/kubectl --server=https://10.240.0.7:6443 --kubeconfig=/home/ubuntu/.kube/config describe rc redis-master --namespace=e2e-tests-kubectl-9mkft'
May  4 03:34:32.409: INFO: stderr: ""
May  4 03:34:32.409: INFO: stdout: "Name:\t\tredis-master\nNamespace:\te2e-tests-kubectl-9mkft\nSelector:\tapp=redis,role=master\nLabels:\t\tapp=redis\n\t\trole=master\nAnnotations:\t<none>\nReplicas:\t1 current / 1 desired\nPods Status:\t1 Running / 0 Waiting / 0 Succeeded / 0 Failed\nPod Template:\n  Labels:\tapp=redis\n\t\trole=master\n  Containers:\n   redis-master:\n    Image:\t\tgcr.io/google_containers/redis:e2e\n    Port:\t\t6379/TCP\n    Environment:\t<none>\n    Mounts:\t\t<none>\n  Volumes:\t\t<none>\nEvents:\n  FirstSeen\tLastSeen\tCount\tFrom\t\t\tSubObjectPath\tType\t\tReason\t\t\tMessage\n  ---------\t--------\t-----\t----\t\t\t-------------\t--------\t------\t\t\t-------\n  7s\t\t7s\t\t1\treplication-controller\t\t\tNormal\t\tSuccessfulCreate\tCreated pod: redis-master-40qpd\n"
May  4 03:34:32.409: INFO: Running '/usr/local/bin/kubectl --server=https://10.240.0.7:6443 --kubeconfig=/home/ubuntu/.kube/config describe service redis-master --namespace=e2e-tests-kubectl-9mkft'
May  4 03:34:32.555: INFO: stderr: ""
May  4 03:34:32.555: INFO: stdout: "Name:\t\t\tredis-master\nNamespace:\t\te2e-tests-kubectl-9mkft\nLabels:\t\t\tapp=redis\n\t\t\trole=master\nAnnotations:\t\t<none>\nSelector:\t\tapp=redis,role=master\nType:\t\t\tClusterIP\nIP:\t\t\t10.152.183.191\nPort:\t\t\t<unset>\t6379/TCP\nEndpoints:\t\t10.1.15.30:6379\nSession Affinity:\tNone\nEvents:\t\t\t<none>\n"
May  4 03:34:32.558: INFO: Running '/usr/local/bin/kubectl --server=https://10.240.0.7:6443 --kubeconfig=/home/ubuntu/.kube/config describe node juju-f88ba1-1'
May  4 03:34:32.723: INFO: stderr: ""
May  4 03:34:32.723: INFO: stdout: "Name:\t\t\tjuju-f88ba1-1\nRole:\t\t\t\nLabels:\t\t\tbeta.kubernetes.io/arch=amd64\n\t\t\tbeta.kubernetes.io/os=linux\n\t\t\tkubernetes.io/hostname=juju-f88ba1-1\nAnnotations:\t\tnode.alpha.kubernetes.io/ttl=0\n\t\t\tvolumes.kubernetes.io/controller-managed-attach-detach=true\nTaints:\t\t\t<none>\nCreationTimestamp:\tThu, 04 May 2017 03:28:01 +0000\nPhase:\t\t\t\nConditions:\n  Type\t\t\tStatus\tLastHeartbeatTime\t\t\tLastTransitionTime\t\t\tReason\t\t\t\tMessage\n  ----\t\t\t------\t-----------------\t\t\t------------------\t\t\t------\t\t\t\t-------\n  OutOfDisk \t\tFalse \tThu, 04 May 2017 03:34:31 +0000 \tThu, 04 May 2017 03:28:01 +0000 \tKubeletHasSufficientDisk \tkubelet has sufficient disk space available\n  MemoryPressure \tFalse \tThu, 04 May 2017 03:34:31 +0000 \tThu, 04 May 2017 03:28:01 +0000 \tKubeletHasSufficientMemory \tkubelet has sufficient memory available\n  DiskPressure \t\tFalse \tThu, 04 May 2017 03:34:31 +0000 \tThu, 04 May 2017 03:28:01 +0000 \tKubeletHasNoDiskPressure \tkubelet has no disk pressure\n  Ready \t\tTrue \tThu, 04 May 2017 03:34:31 +0000 \tThu, 04 May 2017 03:28:01 +0000 \tKubeletReady \t\t\tkubelet is posting ready status. AppArmor enabled\nAddresses:\t\t10.240.0.6,10.240.0.6,juju-f88ba1-1\nCapacity:\n cpu:\t\t1\n memory:\t1736676Ki\n pods:\t\t110\nAllocatable:\n cpu:\t\t1\n memory:\t1634276Ki\n pods:\t\t110\nSystem Info:\n Machine ID:\t\t\tcf70b4a2e2142e3998e801dc5f4487c7\n System UUID:\t\t\tCF70B4A2-E214-2E39-98E8-01DC5F4487C7\n Boot ID:\t\t\t706ed019-ea1b-4766-8dac-fe73a162afd7\n Kernel Version:\t\t4.8.0-45-generic\n OS Image:\t\t\tUbuntu 16.04.2 LTS\n Operating System:\t\tlinux\n Architecture:\t\t\tamd64\n Container Runtime Version:\tdocker://1.12.6\n Kubelet Version:\t\tv1.6.1\n Kube-Proxy Version:\t\tv1.6.1\nExternalID:\t\t\tjuju-f88ba1-1\nNon-terminated Pods:\t\t(8 in total)\n  Namespace\t\t\tName\t\t\t\t\t\t\t\t\tCPU Requests\tCPU Limits\tMemory Requests\tMemory Limits\n  ---------\t\t\t----\t\t\t\t\t\t\t\t\t------------\t----------\t---------------\t-------------\n  default\t\t\tdefault-http-backend-1chhv\t\t\t\t\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  default\t\t\tnginx-ingress-controller-9gdmn\t\t\t\t\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  e2e-tests-kubectl-1ld2x\tupdate-demo-nautilus-dfvvj\t\t\t\t\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  e2e-tests-kubectl-ls37s\tpause\t\t\t\t\t\t\t\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  e2e-tests-kubectl-z5gvh\te2e-test-nginx-deployment-1941701967-d6ms5\t\t\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  e2e-tests-projected-4lbzl\tpod-projected-configmaps-6eb44d5e-307a-11e7-ac11-42010af0000e\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  e2e-tests-replicaset-kxzs5\tmy-hostname-basic-6f047841-307a-11e7-a0ea-42010af0000e-47tx2\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  e2e-tests-secrets-tnzl1\tpod-secrets-87946fe8-307a-11e7-8200-42010af0000e\t\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\nAllocated resources:\n  (Total limits may be over 100 percent, i.e., overcommitted.)\n  CPU Requests\tCPU Limits\tMemory Requests\tMemory Limits\n  ------------\t----------\t---------------\t-------------\n  0 (0%)\t0 (0%)\t\t0 (0%)\t\t0 (0%)\nEvents:\n  FirstSeen\tLastSeen\tCount\tFrom\t\t\t\tSubObjectPath\tType\t\tReason\t\t\tMessage\n  ---------\t--------\t-----\t----\t\t\t\t-------------\t--------\t------\t\t\t-------\n  6m\t\t6m\t\t1\tkubelet, juju-f88ba1-1\t\t\t\tNormal\t\tStarting\t\tStarting kubelet.\n  6m\t\t6m\t\t1\tkubelet, juju-f88ba1-1\t\t\t\tWarning\t\tImageGCFailed\t\tunable to find data for container /\n  6m\t\t6m\t\t7\tkubelet, juju-f88ba1-1\t\t\t\tNormal\t\tNodeHasSufficientDisk\tNode juju-f88ba1-1 status is now: NodeHasSufficientDisk\n  6m\t\t6m\t\t7\tkubelet, juju-f88ba1-1\t\t\t\tNormal\t\tNodeHasSufficientMemory\tNode juju-f88ba1-1 status is now: NodeHasSufficientMemory\n  6m\t\t6m\t\t7\tkubelet, juju-f88ba1-1\t\t\t\tNormal\t\tNodeHasNoDiskPressure\tNode juju-f88ba1-1 status is now: NodeHasNoDiskPressure\n  1m\t\t1m\t\t1\tkube-proxy, juju-f88ba1-1\t\t\tNormal\t\tStarting\t\tStarting kube-proxy.\n  1m\t\t1m\t\t1\tkubelet, juju-f88ba1-1\t\t\t\tNormal\t\tStarting\t\tStarting kubelet.\n  1m\t\t1m\t\t1\tkubelet, juju-f88ba1-1\t\t\t\tWarning\t\tImageGCFailed\t\tunable to find data for container /\n  1m\t\t1m\t\t1\tkubelet, juju-f88ba1-1\t\t\t\tNormal\t\tNodeHasSufficientDisk\tNode juju-f88ba1-1 status is now: NodeHasSufficientDisk\n  1m\t\t1m\t\t1\tkubelet, juju-f88ba1-1\t\t\t\tNormal\t\tNodeHasSufficientMemory\tNode juju-f88ba1-1 status is now: NodeHasSufficientMemory\n  1m\t\t1m\t\t1\tkubelet, juju-f88ba1-1\t\t\t\tNormal\t\tNodeHasNoDiskPressure\tNode juju-f88ba1-1 status is now: NodeHasNoDiskPressure\n"
... skipping 2444 lines ...
May  4 03:34:40.346: INFO: Running '/usr/local/bin/kubectl --server=https://10.240.0.7:6443 --kubeconfig=/home/ubuntu/.kube/config create -f - --namespace=e2e-tests-kubectl-qh7hm'
May  4 03:34:40.688: INFO: stderr: ""
May  4 03:34:40.688: INFO: stdout: "service \"redis-slave\" created\n"
STEP: validating guestbook app
May  4 03:34:40.688: INFO: Waiting for all frontend pods to be Running.
May  4 03:35:40.690: INFO: Waiting for frontend to serve content.
May  4 03:35:40.705: INFO: Failed to get response from guestbook. err: an error on the server ("Error: 'dial tcp 10.1.15.37:80: getsockopt: connection refused'\nTrying to reach: 'http://10.1.15.37:80/guestbook.php?cmd=get&key=messages&value='") has prevented the request from succeeding (get services frontend), response: 
May  4 03:35:46.446: INFO: Trying to add a new entry to the guestbook.
May  4 03:35:52.242: INFO: Failed to get response from guestbook. err: <nil>, response: <br />
<b>Fatal error</b>:  Uncaught exception 'Predis\Connection\ConnectionException' with message 'Connection timed out [tcp://redis-master:6379]' in /usr/local/lib/php/Predis/Connection/AbstractConnection.php:168
Stack trace:
#0 /usr/local/lib/php/Predis/Connection/StreamConnection.php(97): Predis\Connection\AbstractConnection-&gt;onConnectionError('Connection time...', 110)
#1 /usr/local/lib/php/Predis/Connection/StreamConnection.php(58): Predis\Connection\StreamConnection-&gt;tcpStreamInitializer(Object(Predis\Connection\Parameters))
#2 /usr/local/lib/php/Predis/Connection/AbstractConnection.php(94): Predis\Connection\StreamConnection-&gt;createResource()
#3 /usr/local/lib/php/Predis/Connection/StreamConnection.php(158): Predis\Connection\AbstractConnection-&gt;connect()
#4 /usr/local/lib/php/Predis/Connection/AbstractConnection.php(193): Predis\Connection\StreamConnection-&gt;connect()
#5 /usr/local/lib/php/Predis/Connection/StreamConnection.php(184): Predis\Connection\AbstractConnection-&gt;getResource()
#6 /usr/local/lib/php/Predis/Connection/Str in <b>/usr/local/lib/php/Predis/Connection/AbstractConnection.php</b> on line <b>168</b><br />

May  4 03:35:57.250: INFO: Failed to get response from guestbook. err: an error on the server ("Error: 'EOF'\nTrying to reach: 'http://10.1.64.45:80/guestbook.php?cmd=set&key=messages&value=TestEntry'") has prevented the request from succeeding (get services frontend), response: 
May  4 03:36:07.270: INFO: Failed to get response from guestbook. err: <nil>, response: <br />
<b>Fatal error</b>:  Uncaught exception 'Predis\Connection\ConnectionException' with message 'Connection timed out [tcp://redis-master:6379]' in /usr/local/lib/php/Predis/Connection/AbstractConnection.php:168
Stack trace:
#0 /usr/local/lib/php/Predis/Connection/StreamConnection.php(97): Predis\Connection\AbstractConnection-&gt;onConnectionError('Connection time...', 110)
#1 /usr/local/lib/php/Predis/Connection/StreamConnection.php(58): Predis\Connection\StreamConnection-&gt;tcpStreamInitializer(Object(Predis\Connection\Parameters))
#2 /usr/local/lib/php/Predis/Connection/AbstractConnection.php(94): Predis\Connection\StreamConnection-&gt;createResource()
#3 /usr/local/lib/php/Predis/Connection/StreamConnection.php(158): Predis\Connection\AbstractConnection-&gt;connect()
#4 /usr/local/lib/php/Predis/Connection/AbstractConnection.php(193): Predis\Connection\StreamConnection-&gt;connect()
#5 /usr/local/lib/php/Predis/Connection/StreamConnection.php(184): Predis\Connection\AbstractConnection-&gt;getResource()
#6 /usr/local/lib/php/Predis/Connection/Str in <b>/usr/local/lib/php/Predis/Connection/AbstractConnection.php</b> on line <b>168</b><br />

May  4 03:36:17.288: INFO: Failed to get response from guestbook. err: <nil>, response: <br />
<b>Fatal error</b>:  Uncaught exception 'Predis\Connection\ConnectionException' with message 'Connection timed out [tcp://redis-master:6379]' in /usr/local/lib/php/Predis/Connection/AbstractConnection.php:168
Stack trace:
#0 /usr/local/lib/php/Predis/Connection/StreamConnection.php(97): Predis\Connection\AbstractConnection-&gt;onConnectionError('Connection time...', 110)
#1 /usr/local/lib/php/Predis/Connection/StreamConnection.php(58): Predis\Connection\StreamConnection-&gt;tcpStreamInitializer(Object(Predis\Connection\Parameters))
#2 /usr/local/lib/php/Predis/Connection/AbstractConnection.php(94): Predis\Connection\StreamConnection-&gt;createResource()
#3 /usr/local/lib/php/Predis/Connection/StreamConnection.php(158): Predis\Connection\AbstractConnection-&gt;connect()
#4 /usr/local/lib/php/Predis/Connection/AbstractConnection.php(193): Predis\Connection\StreamConnection-&gt;connect()
#5 /usr/local/lib/php/Predis/Connection/StreamConnection.php(184): Predis\Connection\AbstractConnection-&gt;getResource()
#6 /usr/local/lib/php/Predis/Connection/Str in <b>/usr/local/lib/php/Predis/Connection/AbstractConnection.php</b> on line <b>168</b><br />

May  4 03:36:27.309: INFO: Failed to get response from guestbook. err: <nil>, response: <br />
<b>Fatal error</b>:  Uncaught exception 'Predis\Connection\ConnectionException' with message 'Connection timed out [tcp://redis-master:6379]' in /usr/local/lib/php/Predis/Connection/AbstractConnection.php:168
Stack trace:
#0 /usr/local/lib/php/Predis/Connection/StreamConnection.php(97): Predis\Connection\AbstractConnection-&gt;onConnectionError('Connection time...', 110)
#1 /usr/local/lib/php/Predis/Connection/StreamConnection.php(58): Predis\Connection\StreamConnection-&gt;tcpStreamInitializer(Object(Predis\Connection\Parameters))
#2 /usr/local/lib/php/Predis/Connection/AbstractConnection.php(94): Predis\Connection\StreamConnection-&gt;createResource()
#3 /usr/local/lib/php/Predis/Connection/StreamConnection.php(158): Predis\Connection\AbstractConnection-&gt;connect()
#4 /usr/local/lib/php/Predis/Connection/AbstractConnection.php(193): Predis\Connection\StreamConnection-&gt;connect()
... skipping 332 lines ...
STEP: Creating configMap with name projected-configmap-test-volume-map-0e2b5156-307b-11e7-b3f5-42010af0000e
STEP: Creating a pod to test consume configMaps
May  4 03:37:53.505: INFO: Waiting up to 5m0s for pod pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e status to be success or failure
May  4 03:37:53.510: INFO: Waiting for pod pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e in namespace 'e2e-tests-projected-t67tb' status to be 'success or failure'(found phase: "Pending", readiness: false) (4.853934ms elapsed)
STEP: Saw pod success
May  4 03:37:55.515: INFO: Trying to get logs from node juju-f88ba1-1 pod pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e container projected-configmap-volume-test: <nil>
May  4 03:37:55.526: INFO: Failed to get logs from node "juju-f88ba1-1" pod "pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e" container "projected-configmap-volume-test". an error on the server ("unknown") has prevented the request from succeeding (get pods pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e)
STEP: delete the pod
May  4 03:37:55.537: INFO: Waiting for pod pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e to disappear
May  4 03:37:55.539: INFO: Pod pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e no longer exists
May  4 03:37:55.539: INFO: Unexpected error occurred: failed to get logs from pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e for projected-configmap-volume-test: an error on the server ("unknown") has prevented the request from succeeding (get pods pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e)
[AfterEach] [k8s.io] Projected
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:120
STEP: Collecting events from namespace "e2e-tests-projected-t67tb".
STEP: Found 4 events.
May  4 03:37:55.542: INFO: At 2017-05-04 03:37:53 +0000 UTC - event for pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e: {default-scheduler } Scheduled: Successfully assigned pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e to juju-f88ba1-1
May  4 03:37:55.542: INFO: At 2017-05-04 03:37:54 +0000 UTC - event for pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e: {kubelet juju-f88ba1-1} Pulled: Container image "gcr.io/google_containers/mounttest:0.8" already present on machine
... skipping 66 lines ...
• Failure [7.540 seconds]
[k8s.io] Projected
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:650
  should be consumable from pods in volume with mappings as non-root [Conformance] [Volume] [It]
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/projected.go:418

  Expected error:
      <*errors.errorString | 0xc420200ee0>: {
          s: "failed to get logs from pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e for projected-configmap-volume-test: an error on the server (\"unknown\") has prevented the request from succeeding (get pods pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e)",
      }
      failed to get logs from pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e for projected-configmap-volume-test: an error on the server ("unknown") has prevented the request from succeeding (get pods pod-projected-configmaps-0e2c154e-307b-11e7-b3f5-42010af0000e)
  not to have occurred

  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2183
------------------------------
May  4 03:38:00.947: INFO: Running AfterSuite actions on all node

... skipping 905 lines ...
May  4 03:39:07.940: INFO: Unable to read jessie_udp@dns-test-service.e2e-tests-dns-29zd7 from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:07.943: INFO: Unable to read jessie_tcp@dns-test-service.e2e-tests-dns-29zd7 from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:07.946: INFO: Unable to read jessie_udp@dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:07.949: INFO: Unable to read jessie_tcp@dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:07.951: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:07.954: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:07.969: INFO: Lookups using dns-test-2897097e-307b-11e7-b593-42010af0000e failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.e2e-tests-dns-29zd7 wheezy_tcp@dns-test-service.e2e-tests-dns-29zd7 wheezy_udp@dns-test-service.e2e-tests-dns-29zd7.svc wheezy_tcp@dns-test-service.e2e-tests-dns-29zd7.svc wheezy_udp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc wheezy_tcp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.e2e-tests-dns-29zd7 jessie_tcp@dns-test-service.e2e-tests-dns-29zd7 jessie_udp@dns-test-service.e2e-tests-dns-29zd7.svc jessie_tcp@dns-test-service.e2e-tests-dns-29zd7.svc jessie_udp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc jessie_tcp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc]

May  4 03:39:09.850: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:09.853: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:09.856: INFO: Unable to read wheezy_udp@dns-test-service.e2e-tests-dns-29zd7 from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:09.859: INFO: Unable to read wheezy_tcp@dns-test-service.e2e-tests-dns-29zd7 from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:09.861: INFO: Unable to read wheezy_udp@dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
... skipping 5 lines ...
May  4 03:39:09.895: INFO: Unable to read jessie_udp@dns-test-service.e2e-tests-dns-29zd7 from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:09.898: INFO: Unable to read jessie_tcp@dns-test-service.e2e-tests-dns-29zd7 from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:09.901: INFO: Unable to read jessie_udp@dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:09.903: INFO: Unable to read jessie_tcp@dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:09.906: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:09.909: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:10.009: INFO: Lookups using dns-test-2897097e-307b-11e7-b593-42010af0000e failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.e2e-tests-dns-29zd7 wheezy_tcp@dns-test-service.e2e-tests-dns-29zd7 wheezy_udp@dns-test-service.e2e-tests-dns-29zd7.svc wheezy_tcp@dns-test-service.e2e-tests-dns-29zd7.svc wheezy_udp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc wheezy_tcp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.e2e-tests-dns-29zd7 jessie_tcp@dns-test-service.e2e-tests-dns-29zd7 jessie_udp@dns-test-service.e2e-tests-dns-29zd7.svc jessie_tcp@dns-test-service.e2e-tests-dns-29zd7.svc jessie_udp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc jessie_tcp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc]

May  4 03:39:11.850: INFO: Unable to read wheezy_udp@dns-test-service from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:11.854: INFO: Unable to read wheezy_tcp@dns-test-service from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:11.857: INFO: Unable to read wheezy_udp@dns-test-service.e2e-tests-dns-29zd7 from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:11.860: INFO: Unable to read wheezy_tcp@dns-test-service.e2e-tests-dns-29zd7 from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:11.862: INFO: Unable to read wheezy_udp@dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
... skipping 5 lines ...
May  4 03:39:11.894: INFO: Unable to read jessie_udp@dns-test-service.e2e-tests-dns-29zd7 from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:11.897: INFO: Unable to read jessie_tcp@dns-test-service.e2e-tests-dns-29zd7 from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:11.899: INFO: Unable to read jessie_udp@dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:11.902: INFO: Unable to read jessie_tcp@dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:11.904: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:11.907: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:11.924: INFO: Lookups using dns-test-2897097e-307b-11e7-b593-42010af0000e failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.e2e-tests-dns-29zd7 wheezy_tcp@dns-test-service.e2e-tests-dns-29zd7 wheezy_udp@dns-test-service.e2e-tests-dns-29zd7.svc wheezy_tcp@dns-test-service.e2e-tests-dns-29zd7.svc wheezy_udp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc wheezy_tcp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.e2e-tests-dns-29zd7 jessie_tcp@dns-test-service.e2e-tests-dns-29zd7 jessie_udp@dns-test-service.e2e-tests-dns-29zd7.svc jessie_tcp@dns-test-service.e2e-tests-dns-29zd7.svc jessie_udp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc jessie_tcp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc]

May  4 03:39:13.887: INFO: Unable to read jessie_udp@dns-test-service from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:13.889: INFO: Unable to read jessie_tcp@dns-test-service from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:13.892: INFO: Unable to read jessie_udp@dns-test-service.e2e-tests-dns-29zd7 from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:13.895: INFO: Unable to read jessie_tcp@dns-test-service.e2e-tests-dns-29zd7 from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:13.897: INFO: Unable to read jessie_udp@dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:13.900: INFO: Unable to read jessie_tcp@dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:13.902: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:13.905: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc from pod dns-test-2897097e-307b-11e7-b593-42010af0000e: the server could not find the requested resource (get pods dns-test-2897097e-307b-11e7-b593-42010af0000e)
May  4 03:39:13.920: INFO: Lookups using dns-test-2897097e-307b-11e7-b593-42010af0000e failed for: [jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.e2e-tests-dns-29zd7 jessie_tcp@dns-test-service.e2e-tests-dns-29zd7 jessie_udp@dns-test-service.e2e-tests-dns-29zd7.svc jessie_tcp@dns-test-service.e2e-tests-dns-29zd7.svc jessie_udp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc jessie_tcp@_http._tcp.dns-test-service.e2e-tests-dns-29zd7.svc]

May  4 03:39:15.917: INFO: DNS probes using dns-test-2897097e-307b-11e7-b593-42010af0000e succeeded

STEP: deleting the pod
STEP: deleting the test service
STEP: deleting the test headless service
... skipping 745 lines ...
------------------------------
May  4 03:41:34.188: INFO: Running AfterSuite actions on all node


May  4 03:35:00.663: INFO: Running AfterSuite actions on all node
May  4 03:41:34.192: INFO: Running AfterSuite actions on node 1
May  4 03:41:34.193: INFO: Error running cluster/log-dump.sh: fork/exec ../../cluster/log-dump.sh: no such file or directory



Summarizing 1 Failure:

[Fail] [k8s.io] Projected [It] should be consumable from pods in volume with mappings as non-root [Conformance] [Volume] 
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2183

Ran 146 of 588 Specs in 491.052 seconds
FAIL! -- 145 Passed | 1 Failed | 0 Pending | 442 Skipped 

Ginkgo ran 1 suite in 8m21.174774854s
Test Suite Failed
JUJU_E2E_END=1493869294