ResultFAILURE
Tests 1 failed / 112 succeeded
Started2017-03-23 05:49
Elapsed6m18s
Revision

Test Failures


[k8s.io] Variable Expansion should allow substituting values in a container's command [Conformance] 7.68s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Variable\sExpansion\sshould\sallow\ssubstituting\svalues\sin\sa\scontainer\'s\scommand\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/expansion.go:100
Expected error:
    <*errors.errorString | 0xc420f66a10>: {
        s: "failed to get logs from var-expansion-163fd030-0f8d-11e7-a066-42010af0000e for dapi-container: the server could not find the requested resource (get pods var-expansion-163fd030-0f8d-11e7-a066-42010af0000e)",
    }
    failed to get logs from var-expansion-163fd030-0f8d-11e7-a066-42010af0000e for dapi-container: the server could not find the requested resource (get pods var-expansion-163fd030-0f8d-11e7-a066-42010af0000e)
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2167
				from junit_07.xml

Filter through log files | View test history on testgrid


Show 112 Passed Tests

Show 360 Skipped Tests

Error lines from build-log.txt

... skipping 11 lines ...

Mar 23 05:49:24.161: INFO: >>> kubeConfig: /home/ubuntu/.kube/config

Mar 23 05:49:24.163: INFO: Waiting up to 4h0m0s for all (but 0) nodes to be schedulable
Mar 23 05:49:24.476: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready
Mar 23 05:49:24.545: INFO: Waiting for pods to enter Success, but no pods in "kube-system" match label map[name:e2e-image-puller]
Mar 23 05:49:24.602: INFO: The status of Pod heapster-v1.2.0.1-2575396535-5rz4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:24.602: INFO: The status of Pod kube-dns-4101612645-5q2ck is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:24.602: INFO: The status of Pod monitoring-influxdb-grafana-v4-h1zxw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:24.602: INFO: 2 / 5 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
Mar 23 05:49:24.602: INFO: expected 4 pod replicas in namespace 'kube-system', 1 are Running and Ready.
Mar 23 05:49:24.602: INFO: POD                                   NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:24.602: INFO: heapster-v1.2.0.1-2575396535-5rz4d    juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC ContainersNotReady containers with unready status: [heapster eventer heapster-nanny eventer-nanny]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  }]
Mar 23 05:49:24.602: INFO: kube-dns-4101612645-5q2ck             juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns dnsmasq dnsmasq-metrics healthz]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:24.602: INFO: monitoring-influxdb-grafana-v4-h1zxw  juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC ContainersNotReady containers with unready status: [influxdb grafana]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  }]
Mar 23 05:49:24.602: INFO: 
Mar 23 05:49:26.614: INFO: The status of Pod heapster-v1.2.0.1-2575396535-5rz4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:26.614: INFO: The status of Pod kube-dns-4101612645-5q2ck is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:26.614: INFO: The status of Pod monitoring-influxdb-grafana-v4-h1zxw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:26.614: INFO: 1 / 4 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
Mar 23 05:49:26.614: INFO: expected 4 pod replicas in namespace 'kube-system', 1 are Running and Ready.
Mar 23 05:49:26.614: INFO: POD                                   NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:26.614: INFO: heapster-v1.2.0.1-2575396535-5rz4d    juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC ContainersNotReady containers with unready status: [heapster eventer heapster-nanny eventer-nanny]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  }]
Mar 23 05:49:26.614: INFO: kube-dns-4101612645-5q2ck             juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns dnsmasq dnsmasq-metrics healthz]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:26.614: INFO: monitoring-influxdb-grafana-v4-h1zxw  juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC ContainersNotReady containers with unready status: [influxdb grafana]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  }]
Mar 23 05:49:26.614: INFO: 
Mar 23 05:49:28.618: INFO: The status of Pod heapster-v1.2.0.1-2575396535-5rz4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:28.619: INFO: The status of Pod kube-dns-4101612645-5q2ck is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:28.619: INFO: The status of Pod monitoring-influxdb-grafana-v4-h1zxw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:28.619: INFO: 1 / 4 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
Mar 23 05:49:28.619: INFO: expected 4 pod replicas in namespace 'kube-system', 1 are Running and Ready.
Mar 23 05:49:28.619: INFO: POD                                   NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:28.619: INFO: heapster-v1.2.0.1-2575396535-5rz4d    juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC ContainersNotReady containers with unready status: [heapster eventer heapster-nanny eventer-nanny]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  }]
Mar 23 05:49:28.619: INFO: kube-dns-4101612645-5q2ck             juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns dnsmasq dnsmasq-metrics healthz]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:28.619: INFO: monitoring-influxdb-grafana-v4-h1zxw  juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC ContainersNotReady containers with unready status: [influxdb grafana]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  }]
Mar 23 05:49:28.619: INFO: 
Mar 23 05:49:30.614: INFO: The status of Pod heapster-v1.2.0.1-2575396535-5rz4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:30.614: INFO: The status of Pod kube-dns-4101612645-5q2ck is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:30.614: INFO: The status of Pod monitoring-influxdb-grafana-v4-h1zxw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:30.614: INFO: 1 / 4 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
Mar 23 05:49:30.614: INFO: expected 4 pod replicas in namespace 'kube-system', 1 are Running and Ready.
Mar 23 05:49:30.614: INFO: POD                                   NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:30.614: INFO: heapster-v1.2.0.1-2575396535-5rz4d    juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC ContainersNotReady containers with unready status: [heapster eventer heapster-nanny eventer-nanny]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  }]
Mar 23 05:49:30.614: INFO: kube-dns-4101612645-5q2ck             juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns dnsmasq dnsmasq-metrics healthz]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:30.614: INFO: monitoring-influxdb-grafana-v4-h1zxw  juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC ContainersNotReady containers with unready status: [influxdb grafana]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  }]
Mar 23 05:49:30.614: INFO: 
Mar 23 05:49:32.616: INFO: The status of Pod heapster-v1.2.0.1-2575396535-5rz4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:32.616: INFO: The status of Pod kube-dns-4101612645-5q2ck is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:32.616: INFO: The status of Pod monitoring-influxdb-grafana-v4-h1zxw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:32.616: INFO: 1 / 4 pods in namespace 'kube-system' are running and ready (8 seconds elapsed)
Mar 23 05:49:32.616: INFO: expected 4 pod replicas in namespace 'kube-system', 1 are Running and Ready.
Mar 23 05:49:32.616: INFO: POD                                   NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:32.616: INFO: heapster-v1.2.0.1-2575396535-5rz4d    juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC ContainersNotReady containers with unready status: [heapster eventer heapster-nanny eventer-nanny]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  }]
Mar 23 05:49:32.616: INFO: kube-dns-4101612645-5q2ck             juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns dnsmasq dnsmasq-metrics healthz]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:32.616: INFO: monitoring-influxdb-grafana-v4-h1zxw  juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC ContainersNotReady containers with unready status: [influxdb grafana]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  }]
Mar 23 05:49:32.616: INFO: 
Mar 23 05:49:34.618: INFO: The status of Pod heapster-v1.2.0.1-2575396535-5rz4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:34.618: INFO: The status of Pod kube-dns-4101612645-5q2ck is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:34.618: INFO: The status of Pod monitoring-influxdb-grafana-v4-h1zxw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:34.618: INFO: 1 / 4 pods in namespace 'kube-system' are running and ready (10 seconds elapsed)
Mar 23 05:49:34.618: INFO: expected 4 pod replicas in namespace 'kube-system', 1 are Running and Ready.
Mar 23 05:49:34.618: INFO: POD                                   NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:34.618: INFO: heapster-v1.2.0.1-2575396535-5rz4d    juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC ContainersNotReady containers with unready status: [heapster eventer heapster-nanny eventer-nanny]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  }]
Mar 23 05:49:34.618: INFO: kube-dns-4101612645-5q2ck             juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns dnsmasq dnsmasq-metrics healthz]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:34.618: INFO: monitoring-influxdb-grafana-v4-h1zxw  juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC ContainersNotReady containers with unready status: [influxdb grafana]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  }]
Mar 23 05:49:34.618: INFO: 
Mar 23 05:49:36.666: INFO: The status of Pod heapster-v1.2.0.1-2575396535-5rz4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:36.666: INFO: The status of Pod kube-dns-4101612645-5q2ck is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:36.666: INFO: The status of Pod monitoring-influxdb-grafana-v4-h1zxw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:36.666: INFO: 1 / 4 pods in namespace 'kube-system' are running and ready (12 seconds elapsed)
Mar 23 05:49:36.666: INFO: expected 4 pod replicas in namespace 'kube-system', 1 are Running and Ready.
Mar 23 05:49:36.666: INFO: POD                                   NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:36.666: INFO: heapster-v1.2.0.1-2575396535-5rz4d    juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC ContainersNotReady containers with unready status: [heapster eventer heapster-nanny eventer-nanny]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  }]
Mar 23 05:49:36.666: INFO: kube-dns-4101612645-5q2ck             juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns dnsmasq dnsmasq-metrics healthz]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:36.666: INFO: monitoring-influxdb-grafana-v4-h1zxw  juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC ContainersNotReady containers with unready status: [influxdb grafana]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  }]
Mar 23 05:49:36.666: INFO: 
Mar 23 05:49:38.621: INFO: The status of Pod heapster-v1.2.0.1-2575396535-5rz4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:38.621: INFO: The status of Pod kube-dns-4101612645-5q2ck is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:38.621: INFO: The status of Pod monitoring-influxdb-grafana-v4-h1zxw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:38.621: INFO: 1 / 4 pods in namespace 'kube-system' are running and ready (14 seconds elapsed)
Mar 23 05:49:38.621: INFO: expected 4 pod replicas in namespace 'kube-system', 1 are Running and Ready.
Mar 23 05:49:38.621: INFO: POD                                   NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:38.621: INFO: heapster-v1.2.0.1-2575396535-5rz4d    juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC ContainersNotReady containers with unready status: [heapster eventer heapster-nanny eventer-nanny]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  }]
Mar 23 05:49:38.621: INFO: kube-dns-4101612645-5q2ck             juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns dnsmasq dnsmasq-metrics healthz]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:38.621: INFO: monitoring-influxdb-grafana-v4-h1zxw  juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC ContainersNotReady containers with unready status: [influxdb grafana]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  }]
Mar 23 05:49:38.621: INFO: 
Mar 23 05:49:40.616: INFO: The status of Pod heapster-v1.2.0.1-2575396535-5rz4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:40.616: INFO: The status of Pod kube-dns-4101612645-5q2ck is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:40.616: INFO: The status of Pod monitoring-influxdb-grafana-v4-h1zxw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:40.616: INFO: 1 / 4 pods in namespace 'kube-system' are running and ready (16 seconds elapsed)
Mar 23 05:49:40.616: INFO: expected 4 pod replicas in namespace 'kube-system', 1 are Running and Ready.
Mar 23 05:49:40.616: INFO: POD                                   NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:40.616: INFO: heapster-v1.2.0.1-2575396535-5rz4d    juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC ContainersNotReady containers with unready status: [heapster eventer heapster-nanny eventer-nanny]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  }]
Mar 23 05:49:40.616: INFO: kube-dns-4101612645-5q2ck             juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns dnsmasq dnsmasq-metrics healthz]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:40.616: INFO: monitoring-influxdb-grafana-v4-h1zxw  juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC ContainersNotReady containers with unready status: [influxdb grafana]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  }]
Mar 23 05:49:40.616: INFO: 
Mar 23 05:49:42.615: INFO: The status of Pod heapster-v1.2.0.1-2575396535-5rz4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:42.615: INFO: The status of Pod kube-dns-4101612645-5q2ck is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:42.615: INFO: The status of Pod monitoring-influxdb-grafana-v4-h1zxw is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:42.615: INFO: 1 / 4 pods in namespace 'kube-system' are running and ready (18 seconds elapsed)
Mar 23 05:49:42.615: INFO: expected 4 pod replicas in namespace 'kube-system', 1 are Running and Ready.
Mar 23 05:49:42.615: INFO: POD                                   NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:42.615: INFO: heapster-v1.2.0.1-2575396535-5rz4d    juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC ContainersNotReady containers with unready status: [heapster eventer heapster-nanny eventer-nanny]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  }]
Mar 23 05:49:42.615: INFO: kube-dns-4101612645-5q2ck             juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns dnsmasq dnsmasq-metrics healthz]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:42.615: INFO: monitoring-influxdb-grafana-v4-h1zxw  juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC ContainersNotReady containers with unready status: [influxdb grafana]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:54 +0000 UTC  }]
Mar 23 05:49:42.615: INFO: 
Mar 23 05:49:44.618: INFO: The status of Pod heapster-v1.2.0.1-2575396535-5rz4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:44.618: INFO: The status of Pod kube-dns-4101612645-5q2ck is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:44.618: INFO: 2 / 4 pods in namespace 'kube-system' are running and ready (20 seconds elapsed)
Mar 23 05:49:44.618: INFO: expected 4 pod replicas in namespace 'kube-system', 2 are Running and Ready.
Mar 23 05:49:44.618: INFO: POD                                 NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:44.618: INFO: heapster-v1.2.0.1-2575396535-5rz4d  juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC ContainersNotReady containers with unready status: [heapster eventer heapster-nanny eventer-nanny]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  }]
Mar 23 05:49:44.618: INFO: kube-dns-4101612645-5q2ck           juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns dnsmasq dnsmasq-metrics healthz]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:44.618: INFO: 
Mar 23 05:49:46.617: INFO: The status of Pod heapster-v1.2.0.1-2575396535-5rz4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:46.617: INFO: The status of Pod kube-dns-4101612645-5q2ck is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:46.617: INFO: 2 / 4 pods in namespace 'kube-system' are running and ready (22 seconds elapsed)
Mar 23 05:49:46.617: INFO: expected 4 pod replicas in namespace 'kube-system', 2 are Running and Ready.
Mar 23 05:49:46.617: INFO: POD                                 NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:46.617: INFO: heapster-v1.2.0.1-2575396535-5rz4d  juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC ContainersNotReady containers with unready status: [heapster eventer heapster-nanny eventer-nanny]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  }]
Mar 23 05:49:46.617: INFO: kube-dns-4101612645-5q2ck           juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns dnsmasq dnsmasq-metrics healthz]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:46.617: INFO: 
Mar 23 05:49:48.629: INFO: The status of Pod heapster-v1.2.0.1-2575396535-5rz4d is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:48.629: INFO: The status of Pod kube-dns-4101612645-5q2ck is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:48.629: INFO: 2 / 4 pods in namespace 'kube-system' are running and ready (24 seconds elapsed)
Mar 23 05:49:48.629: INFO: expected 4 pod replicas in namespace 'kube-system', 2 are Running and Ready.
Mar 23 05:49:48.629: INFO: POD                                 NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:48.629: INFO: heapster-v1.2.0.1-2575396535-5rz4d  juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC ContainersNotReady containers with unready status: [heapster eventer heapster-nanny eventer-nanny]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:14 +0000 UTC  }]
Mar 23 05:49:48.629: INFO: kube-dns-4101612645-5q2ck           juju-40f8e1-2  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns dnsmasq dnsmasq-metrics healthz]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:48.629: INFO: 
Mar 23 05:49:50.620: INFO: The status of Pod heapster-v1.2.0.1-1298358222-48781 is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:50.621: INFO: The status of Pod kube-dns-4101612645-5q2ck is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:50.621: INFO: 3 / 5 pods in namespace 'kube-system' are running and ready (26 seconds elapsed)
Mar 23 05:49:50.621: INFO: expected 4 pod replicas in namespace 'kube-system', 2 are Running and Ready.
Mar 23 05:49:50.621: INFO: POD                                 NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:50.621: INFO: heapster-v1.2.0.1-1298358222-48781  juju-40f8e1-1  Pending         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:49 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:49 +0000 UTC ContainersNotReady containers with unready status: [heapster eventer heapster-nanny eventer-nanny]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:49:49 +0000 UTC  }]
Mar 23 05:49:50.621: INFO: kube-dns-4101612645-5q2ck           juju-40f8e1-2  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:50.621: INFO: 
Mar 23 05:49:52.615: INFO: The status of Pod kube-dns-4101612645-5q2ck is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:52.615: INFO: 3 / 4 pods in namespace 'kube-system' are running and ready (28 seconds elapsed)
Mar 23 05:49:52.615: INFO: expected 4 pod replicas in namespace 'kube-system', 3 are Running and Ready.
Mar 23 05:49:52.615: INFO: POD                        NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:52.615: INFO: kube-dns-4101612645-5q2ck  juju-40f8e1-2  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:52.615: INFO: 
Mar 23 05:49:54.613: INFO: The status of Pod kube-dns-4101612645-5q2ck is Running (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
Mar 23 05:49:54.613: INFO: 3 / 4 pods in namespace 'kube-system' are running and ready (30 seconds elapsed)
Mar 23 05:49:54.613: INFO: expected 4 pod replicas in namespace 'kube-system', 3 are Running and Ready.
Mar 23 05:49:54.613: INFO: POD                        NODE           PHASE    GRACE  CONDITIONS
Mar 23 05:49:54.613: INFO: kube-dns-4101612645-5q2ck  juju-40f8e1-2  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  } {Ready False 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC ContainersNotReady containers with unready status: [kubedns]} {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-23 05:48:55 +0000 UTC  }]
Mar 23 05:49:54.613: INFO: 
Mar 23 05:49:56.651: INFO: 4 / 4 pods in namespace 'kube-system' are running and ready (32 seconds elapsed)
... skipping 1722 lines ...
Mar 23 05:50:27.871: INFO: Unable to read jessie_udp@dns-test-service.e2e-tests-dns-g71p5 from pod dns-test-8d064774-0f8c-11e7-88d0-42010af0000e: the server could not find the requested resource (get pods dns-test-8d064774-0f8c-11e7-88d0-42010af0000e)
Mar 23 05:50:27.875: INFO: Unable to read jessie_tcp@dns-test-service.e2e-tests-dns-g71p5 from pod dns-test-8d064774-0f8c-11e7-88d0-42010af0000e: the server could not find the requested resource (get pods dns-test-8d064774-0f8c-11e7-88d0-42010af0000e)
Mar 23 05:50:27.877: INFO: Unable to read jessie_udp@dns-test-service.e2e-tests-dns-g71p5.svc from pod dns-test-8d064774-0f8c-11e7-88d0-42010af0000e: the server could not find the requested resource (get pods dns-test-8d064774-0f8c-11e7-88d0-42010af0000e)
Mar 23 05:50:27.880: INFO: Unable to read jessie_tcp@dns-test-service.e2e-tests-dns-g71p5.svc from pod dns-test-8d064774-0f8c-11e7-88d0-42010af0000e: the server could not find the requested resource (get pods dns-test-8d064774-0f8c-11e7-88d0-42010af0000e)
Mar 23 05:50:27.883: INFO: Unable to read jessie_udp@_http._tcp.dns-test-service.e2e-tests-dns-g71p5.svc from pod dns-test-8d064774-0f8c-11e7-88d0-42010af0000e: the server could not find the requested resource (get pods dns-test-8d064774-0f8c-11e7-88d0-42010af0000e)
Mar 23 05:50:28.500: INFO: Unable to read jessie_tcp@_http._tcp.dns-test-service.e2e-tests-dns-g71p5.svc from pod dns-test-8d064774-0f8c-11e7-88d0-42010af0000e: the server could not find the requested resource (get pods dns-test-8d064774-0f8c-11e7-88d0-42010af0000e)
Mar 23 05:50:28.569: INFO: Lookups using dns-test-8d064774-0f8c-11e7-88d0-42010af0000e failed for: [wheezy_udp@dns-test-service wheezy_tcp@dns-test-service wheezy_udp@dns-test-service.e2e-tests-dns-g71p5 wheezy_tcp@dns-test-service.e2e-tests-dns-g71p5 wheezy_udp@dns-test-service.e2e-tests-dns-g71p5.svc wheezy_tcp@dns-test-service.e2e-tests-dns-g71p5.svc wheezy_udp@_http._tcp.dns-test-service.e2e-tests-dns-g71p5.svc wheezy_tcp@_http._tcp.dns-test-service.e2e-tests-dns-g71p5.svc jessie_udp@dns-test-service jessie_tcp@dns-test-service jessie_udp@dns-test-service.e2e-tests-dns-g71p5 jessie_tcp@dns-test-service.e2e-tests-dns-g71p5 jessie_udp@dns-test-service.e2e-tests-dns-g71p5.svc jessie_tcp@dns-test-service.e2e-tests-dns-g71p5.svc jessie_udp@_http._tcp.dns-test-service.e2e-tests-dns-g71p5.svc jessie_tcp@_http._tcp.dns-test-service.e2e-tests-dns-g71p5.svc]

Mar 23 05:50:29.912: INFO: DNS probes using dns-test-8d064774-0f8c-11e7-88d0-42010af0000e succeeded

STEP: deleting the pod
STEP: deleting the test service
STEP: deleting the test headless service
... skipping 267 lines ...
[BeforeEach] [k8s.io] Services
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:90
[It] should serve a basic endpoint from pods [Conformance]
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/service.go:169
STEP: creating service endpoint-test2 in namespace e2e-tests-services-2n710
STEP: waiting up to 1m0s for service endpoint-test2 in namespace e2e-tests-services-2n710 to expose endpoints map[]
Mar 23 05:50:24.886: INFO: Get endpoints failed (3.638155ms elapsed, ignoring for 5s): endpoints "endpoint-test2" not found
Mar 23 05:50:25.889: INFO: Get endpoints failed (1.006311343s elapsed, ignoring for 5s): endpoints "endpoint-test2" not found
Mar 23 05:50:26.892: INFO: successfully validated that service endpoint-test2 in namespace e2e-tests-services-2n710 exposes endpoints map[] (2.009031649s elapsed)
STEP: creating pod pod1 in namespace e2e-tests-services-2n710
STEP: waiting up to 1m0s for service endpoint-test2 in namespace e2e-tests-services-2n710 to expose endpoints map[pod1:[80]]
Mar 23 05:50:30.937: INFO: Unexpected endpoints: found map[], expected map[pod1:[80]] (4.035730546s elapsed, will retry)
Mar 23 05:50:36.107: INFO: Unexpected endpoints: found map[], expected map[pod1:[80]] (9.205750955s elapsed, will retry)
Mar 23 05:50:41.130: INFO: Unexpected endpoints: found map[], expected map[pod1:[80]] (14.229096039s elapsed, will retry)
... skipping 1365 lines ...
Mar 23 05:51:39.531: INFO: ForEach: Found 1 pods from the filter.  Now looping through them.
Mar 23 05:51:39.531: INFO: Running '/usr/local/bin/kubectl --server=https://10.240.0.7:6443 --kubeconfig=/home/ubuntu/.kube/config describe pod redis-master-r32bv --namespace=e2e-tests-kubectl-3swtb'
Mar 23 05:51:39.649: INFO: stderr: ""
Mar 23 05:51:39.649: INFO: stdout: "Name:\t\tredis-master-r32bv\nNamespace:\te2e-tests-kubectl-3swtb\nNode:\t\tjuju-40f8e1-1/10.240.0.8\nStart Time:\tThu, 23 Mar 2017 05:50:38 +0000\nLabels:\t\tapp=redis\n\t\trole=master\nStatus:\t\tRunning\nIP:\t\t10.1.92.30\nControllers:\tReplicationController/redis-master\nContainers:\n  redis-master:\n    Container ID:\tdocker://210e013c9659c759d631d1818fe7f643d0dfd1005eb7bd7de9f11e8b5c8d7337\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, 23 Mar 2017 05:51:38 +0000\n    Ready:\t\tTrue\n    Restart Count:\t0\n    Volume Mounts:\n      /var/run/secrets/kubernetes.io/serviceaccount from default-token-fzxvk (ro)\n    Environment Variables:\t<none>\nConditions:\n  Type\t\tStatus\n  Initialized \tTrue \n  Ready \tTrue \n  PodScheduled \tTrue \nVolumes:\n  default-token-fzxvk:\n    Type:\tSecret (a volume populated by a Secret)\n    SecretName:\tdefault-token-fzxvk\nQoS Class:\tBestEffort\nTolerations:\t<none>\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  1m\t\t1m\t\t1\t{default-scheduler }\t\t\t\t\tNormal\t\tScheduled\tSuccessfully assigned redis-master-r32bv to juju-40f8e1-1\n  56s\t\t56s\t\t1\t{kubelet juju-40f8e1-1}\tspec.containers{redis-master}\tNormal\t\tPulling\t\tpulling image \"gcr.io/google_containers/redis:e2e\"\n  2s\t\t2s\t\t1\t{kubelet juju-40f8e1-1}\tspec.containers{redis-master}\tNormal\t\tPulled\t\tSuccessfully pulled image \"gcr.io/google_containers/redis:e2e\"\n  1s\t\t1s\t\t1\t{kubelet juju-40f8e1-1}\tspec.containers{redis-master}\tNormal\t\tCreated\t\tCreated container with docker id 210e013c9659; Security:[seccomp=unconfined]\n  1s\t\t1s\t\t1\t{kubelet juju-40f8e1-1}\tspec.containers{redis-master}\tNormal\t\tStarted\t\tStarted container with docker id 210e013c9659\n"
Mar 23 05:51:39.650: 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-3swtb'
Mar 23 05:51:39.765: INFO: stderr: ""
Mar 23 05:51:39.765: INFO: stdout: "Name:\t\tredis-master\nNamespace:\te2e-tests-kubectl-3swtb\nImage(s):\tgcr.io/google_containers/redis:e2e\nSelector:\tapp=redis,role=master\nLabels:\t\tapp=redis\n\t\trole=master\nReplicas:\t1 current / 1 desired\nPods Status:\t1 Running / 0 Waiting / 0 Succeeded / 0 Failed\nNo volumes.\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  1m\t\t1m\t\t1\t{replication-controller }\t\t\tNormal\t\tSuccessfulCreate\tCreated pod: redis-master-r32bv\n"
Mar 23 05:51:39.765: 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-3swtb'
Mar 23 05:51:39.895: INFO: stderr: ""
Mar 23 05:51:39.895: INFO: stdout: "Name:\t\t\tredis-master\nNamespace:\t\te2e-tests-kubectl-3swtb\nLabels:\t\t\tapp=redis\n\t\t\trole=master\nSelector:\t\tapp=redis,role=master\nType:\t\t\tClusterIP\nIP:\t\t\t10.152.183.63\nPort:\t\t\t<unset>\t6379/TCP\nEndpoints:\t\t10.1.92.30:6379\nSession Affinity:\tNone\nNo events.\n"
Mar 23 05:51:39.897: INFO: Running '/usr/local/bin/kubectl --server=https://10.240.0.7:6443 --kubeconfig=/home/ubuntu/.kube/config describe node juju-40f8e1-1'
Mar 23 05:51:40.029: INFO: stderr: ""
Mar 23 05:51:40.029: INFO: stdout: "Name:\t\t\tjuju-40f8e1-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-40f8e1-1\nTaints:\t\t\t<none>\nCreationTimestamp:\tThu, 23 Mar 2017 05:48:48 +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, 23 Mar 2017 05:51:34 +0000 \tThu, 23 Mar 2017 05:48:48 +0000 \tKubeletHasSufficientDisk \tkubelet has sufficient disk space available\n  MemoryPressure \tFalse \tThu, 23 Mar 2017 05:51:34 +0000 \tThu, 23 Mar 2017 05:48:48 +0000 \tKubeletHasSufficientMemory \tkubelet has sufficient memory available\n  DiskPressure \t\tFalse \tThu, 23 Mar 2017 05:51:34 +0000 \tThu, 23 Mar 2017 05:48:48 +0000 \tKubeletHasNoDiskPressure \tkubelet has no disk pressure\n  Ready \t\tTrue \tThu, 23 Mar 2017 05:51:34 +0000 \tThu, 23 Mar 2017 05:48:48 +0000 \tKubeletReady \t\t\tkubelet is posting ready status. AppArmor enabled\nAddresses:\t\t10.240.0.8,10.240.0.8,juju-40f8e1-1\nCapacity:\n alpha.kubernetes.io/nvidia-gpu:\t0\n cpu:\t\t\t\t\t1\n memory:\t\t\t\t1737072Ki\n pods:\t\t\t\t\t110\nAllocatable:\n alpha.kubernetes.io/nvidia-gpu:\t0\n cpu:\t\t\t\t\t1\n memory:\t\t\t\t1737072Ki\n pods:\t\t\t\t\t110\nSystem Info:\n Machine ID:\t\t\t\t\t986016e8625787869a57ed78e919c1f4\n System UUID:\t\t\t\t\t986016E8-6257-8786-9A57-ED78E919C1F4\n Boot ID:\t\t\t\t\t10248cea-b153-438f-8dbc-e3a0a9d64dba\n Kernel Version:\t\t\t\t4.4.0-66-generic\n OS Image:\t\t\t\t\tUbuntu 16.04.2 LTS\n Operating System:\t\t\t\tlinux\n Architecture:\t\t\t\t\tamd64\n Container Runtime Version:\t\t\tdocker://1.12.6\n Kubelet Version:\t\t\t\tv1.5.3\n Kube-Proxy Version:\t\t\t\tv1.5.3\nExternalID:\t\t\t\t\tjuju-40f8e1-1\nNon-terminated Pods:\t\t\t\t(12 in total)\n  Namespace\t\t\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----------\t---------------\t-------------\n  default\t\t\t\t\tdefault-http-backend-xx0z5\t\t\t\t\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  default\t\t\t\t\tnginx-ingress-controller-ts1rp\t\t\t\t\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  e2e-tests-containers-v10fm\t\t\tclient-containers-c07925b7-0f8c-11e7-a685-42010af0000e\t\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  e2e-tests-downward-api-q7c12\t\t\tlabelsupdatec1d30b89-0f8c-11e7-bca6-42010af0000e\t\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  e2e-tests-kubectl-3swtb\t\t\tredis-master-r32bv\t\t\t\t\t\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  e2e-tests-kubectl-8gstr\t\t\tredis-master-jj9qr\t\t\t\t\t\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  e2e-tests-kubectl-c6gv7\t\t\tfrontend-88237173-wgfd5\t\t\t\t\t\t\t100m (10%)\t0 (0%)\t\t100Mi (5%)\t0 (0%)\n  e2e-tests-pod-network-test-j1jk9\t\tnetserver-1\t\t\t\t\t\t\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  e2e-tests-replicaset-z1642\t\t\tmy-hostname-basic-abf2d17d-0f8c-11e7-8f3c-42010af0000e-gfg1d\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  e2e-tests-replication-controller-hb7vz\tmy-hostname-basic-95d44135-0f8c-11e7-9e5f-42010af0000e-1dkls\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\t\t0 (0%)\n  kube-system\t\t\t\t\theapster-v1.2.0.1-1298358222-48781\t\t\t\t\t288m (28%)\t288m (28%)\t596576Ki (34%)\t596576Ki (34%)\n  kube-system\t\t\t\t\tkubernetes-dashboard-3543765157-7j67p\t\t\t\t\t100m (10%)\t100m (10%)\t50Mi (2%)\t50Mi (2%)\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  488m (48%)\t388m (38%)\t750176Ki (43%)\t647776Ki (37%)\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  2m\t\t2m\t\t1\t{kube-proxy juju-40f8e1-1}\t\t\tNormal\t\tStarting\t\tStarting kube-proxy.\n  2m\t\t2m\t\t1\t{kubelet juju-40f8e1-1}\t\t\t\tNormal\t\tStarting\t\tStarting kubelet.\n  2m\t\t2m\t\t1\t{kubelet juju-40f8e1-1}\t\t\t\tWarning\t\tImageGCFailed\t\tunable to find data for container /\n  2m\t\t2m\t\t2\t{kubelet juju-40f8e1-1}\t\t\t\tNormal\t\tNodeHasSufficientDisk\tNode juju-40f8e1-1 status is now: NodeHasSufficientDisk\n  2m\t\t2m\t\t2\t{kubelet juju-40f8e1-1}\t\t\t\tNormal\t\tNodeHasSufficientMemory\tNode juju-40f8e1-1 status is now: NodeHasSufficientMemory\n  2m\t\t2m\t\t2\t{kubelet juju-40f8e1-1}\t\t\t\tNormal\t\tNodeHasNoDiskPressure\tNode juju-40f8e1-1 status is now: NodeHasNoDiskPressure\n"
... skipping 2424 lines ...
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/expansion.go:100
STEP: Creating a pod to test substitution in container's command
Mar 23 05:53:49.624: INFO: Waiting up to 5m0s for pod var-expansion-163fd030-0f8d-11e7-a066-42010af0000e status to be success or failure
Mar 23 05:53:49.628: INFO: Waiting for pod var-expansion-163fd030-0f8d-11e7-a066-42010af0000e in namespace 'e2e-tests-var-expansion-v9333' status to be 'success or failure'(found phase: "Pending", readiness: false) (3.119391ms elapsed)
STEP: Saw pod success
Mar 23 05:53:51.634: INFO: Trying to get logs from node juju-40f8e1-1 pod var-expansion-163fd030-0f8d-11e7-a066-42010af0000e container dapi-container: <nil>
Mar 23 05:53:51.814: INFO: Failed to get logs from node "juju-40f8e1-1" pod "var-expansion-163fd030-0f8d-11e7-a066-42010af0000e" container "dapi-container". the server could not find the requested resource (get pods var-expansion-163fd030-0f8d-11e7-a066-42010af0000e)
STEP: delete the pod
Mar 23 05:53:51.832: INFO: Waiting for pod var-expansion-163fd030-0f8d-11e7-a066-42010af0000e to disappear
Mar 23 05:53:51.837: INFO: Pod var-expansion-163fd030-0f8d-11e7-a066-42010af0000e no longer exists
Mar 23 05:53:51.837: INFO: Unexpected error occurred: failed to get logs from var-expansion-163fd030-0f8d-11e7-a066-42010af0000e for dapi-container: the server could not find the requested resource (get pods var-expansion-163fd030-0f8d-11e7-a066-42010af0000e)
[AfterEach] [k8s.io] Variable Expansion
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:142
STEP: Collecting events from namespace "e2e-tests-var-expansion-v9333".
STEP: Found 4 events.
Mar 23 05:53:51.841: INFO: At 2017-03-23 05:53:49 +0000 UTC - event for var-expansion-163fd030-0f8d-11e7-a066-42010af0000e: {default-scheduler } Scheduled: Successfully assigned var-expansion-163fd030-0f8d-11e7-a066-42010af0000e to juju-40f8e1-1
Mar 23 05:53:51.841: INFO: At 2017-03-23 05:53:50 +0000 UTC - event for var-expansion-163fd030-0f8d-11e7-a066-42010af0000e: {kubelet juju-40f8e1-1} Pulled: Container image "gcr.io/google_containers/busybox:1.24" already present on machine
... skipping 38 lines ...
• Failure [7.677 seconds]
[k8s.io] Variable Expansion
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:826
  should allow substituting values in a container's command [Conformance] [It]
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/common/expansion.go:100

  Expected error:
      <*errors.errorString | 0xc420f66a10>: {
          s: "failed to get logs from var-expansion-163fd030-0f8d-11e7-a066-42010af0000e for dapi-container: the server could not find the requested resource (get pods var-expansion-163fd030-0f8d-11e7-a066-42010af0000e)",
      }
      failed to get logs from var-expansion-163fd030-0f8d-11e7-a066-42010af0000e for dapi-container: the server could not find the requested resource (get pods var-expansion-163fd030-0f8d-11e7-a066-42010af0000e)
  not to have occurred

  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2167
------------------------------
[BeforeEach] [k8s.io] Networking
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:141
... skipping 585 lines ...
  /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:826
    should support proxy with --port 0 [Conformance]
    /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/kubectl.go:1303
------------------------------
SS
------------------------------
Mar 23 05:55:33.776: INFO: Error running cluster/log-dump.sh: fork/exec ../../cluster/log-dump.sh: no such file or directory



Summarizing 1 Failure:

[Fail] [k8s.io] Variable Expansion [It] should allow substituting values in a container's command [Conformance] 
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/util.go:2167

Ran 113 of 473 Specs in 369.798 seconds
FAIL! -- 112 Passed | 1 Failed | 0 Pending | 360 Skipped 

Ginkgo ran 1 suite in 6m18.264696683s
Test Suite Failed
JUJU_E2E_END=1490248533