This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 20 succeeded
Started2020-01-17 13:40
Elapsed50m35s
Revision
Buildergke-prow-default-pool-cf4891d4-mzhc
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/7c0813e5-87ab-49ec-895c-9bcc039d0b0e/targets/test'}}
podd4cdf2e0-392e-11ea-8780-468616f72408
resultstorehttps://source.cloud.google.com/results/invocations/7c0813e5-87ab-49ec-895c-9bcc039d0b0e/targets/test
infra-commitf3c464c7f
job-versionv1.17.2-beta.0
master_os_imagecos-77-12371-89-0
node_os_imagecos-77-12371-89-0
podd4cdf2e0-392e-11ea-8780-468616f72408
revisionv1.17.2-beta.0

Test Failures


listResources After 1m25s

Failed to list resources (error during ./cluster/gce/list-resources.sh: exit status 2):
Project: k8s-ingress-boskos-13
Region: 
Zone: 
Instance prefix: test-6724261826
Network: test-6724261826
Provider: gce


[ compute instance-templates ]



[ compute instance-groups ]



[ compute instances ]

				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 20 Passed Tests

Show 4839 Skipped Tests

Error lines from build-log.txt

... skipping 15 lines ...
I0117 13:40:45.702] process 49 exited with code 0 after 0.0m
I0117 13:40:45.702] Will upload results to gs://kubernetes-jenkins/logs using pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com
I0117 13:40:45.703] Root: /workspace
I0117 13:40:45.703] cd to /workspace
I0117 13:40:45.703] Configure environment...
I0117 13:40:45.704] Call:  git show -s --format=format:%ct HEAD
W0117 13:40:45.708] fatal: not a git repository (or any of the parent directories): .git
I0117 13:40:45.708] process 62 exited with code 128 after 0.0m
W0117 13:40:45.708] Unable to print commit date for HEAD
I0117 13:40:45.708] Call:  gcloud auth activate-service-account --key-file=/etc/service-account/service-account.json
W0117 13:40:46.226] Activated service account credentials for: [pr-kubekins@kubernetes-jenkins-pull.iam.gserviceaccount.com]
I0117 13:40:46.576] process 63 exited with code 0 after 0.0m
I0117 13:40:46.577] Call:  gcloud config get-value account
... skipping 156 lines ...
W0117 13:41:42.911] Project: k8s-ingress-boskos-13
W0117 13:41:42.911] Network Project: k8s-ingress-boskos-13
W0117 13:41:42.911] Zone: us-west1-b
W0117 13:41:44.935] INSTANCE_GROUPS=
W0117 13:41:44.935] NODE_NAMES=
I0117 13:41:45.036] Bringing down cluster
W0117 13:41:47.423] ERROR: (gcloud.compute.instances.list) Some requests did not succeed:
W0117 13:41:47.423]  - Invalid value for field 'zone': 'asia-northeast3-a'. Unknown zone.
W0117 13:41:47.424]  - Invalid value for field 'zone': 'asia-northeast3-b'. Unknown zone.
W0117 13:41:47.424]  - Invalid value for field 'zone': 'asia-northeast3-c'. Unknown zone.
W0117 13:41:47.424] 
W0117 13:41:49.149] ERROR: (gcloud.compute.instances.list) Some requests did not succeed:
W0117 13:41:49.149]  - Invalid value for field 'zone': 'asia-northeast3-a'. Unknown zone.
W0117 13:41:49.149]  - Invalid value for field 'zone': 'asia-northeast3-b'. Unknown zone.
W0117 13:41:49.150]  - Invalid value for field 'zone': 'asia-northeast3-c'. Unknown zone.
W0117 13:41:49.150] 
W0117 13:41:53.051] ERROR: (gcloud.compute.instances.list) Some requests did not succeed:
W0117 13:41:53.051]  - Invalid value for field 'zone': 'asia-northeast3-a'. Unknown zone.
W0117 13:41:53.052]  - Invalid value for field 'zone': 'asia-northeast3-b'. Unknown zone.
W0117 13:41:53.052]  - Invalid value for field 'zone': 'asia-northeast3-c'. Unknown zone.
W0117 13:41:53.052] 
W0117 13:41:59.858] ERROR: (gcloud.compute.instances.list) Some requests did not succeed:
W0117 13:41:59.858]  - Invalid value for field 'zone': 'asia-northeast3-a'. Unknown zone.
W0117 13:41:59.859]  - Invalid value for field 'zone': 'asia-northeast3-b'. Unknown zone.
W0117 13:41:59.859]  - Invalid value for field 'zone': 'asia-northeast3-c'. Unknown zone.
W0117 13:41:59.859] 
I0117 13:42:07.247] Deleting firewall rules remaining in network test-6724261826: 
W0117 13:42:09.248] W0117 13:42:09.248726    1001 loader.go:223] Config not found: /workspace/.kube/config
... skipping 159 lines ...
W0117 13:44:48.423] Trying to find master named 'test-6724261826-master'
W0117 13:44:48.423] Looking for address 'test-6724261826-master-ip'
W0117 13:44:49.324] Using master: test-6724261826-master (external IP: 35.233.179.176; internal IP: (not set))
I0117 13:44:49.425] Waiting up to 300 seconds for cluster initialization.
I0117 13:44:49.425] 
I0117 13:44:49.426]   This will continually check to see if the API for kubernetes is reachable.
I0117 13:44:49.426]   This may time out if there was some uncaught error during start up.
I0117 13:44:49.426] 
I0117 13:45:54.124] ..............Kubernetes cluster created.
I0117 13:45:54.266] Cluster "k8s-ingress-boskos-13_test-6724261826" set.
I0117 13:45:54.412] User "k8s-ingress-boskos-13_test-6724261826" set.
I0117 13:45:54.558] Context "k8s-ingress-boskos-13_test-6724261826" created.
I0117 13:45:54.717] Switched to context "k8s-ingress-boskos-13_test-6724261826".
... skipping 24 lines ...
I0117 13:46:34.375] NAME                                STATUS                     ROLES    AGE   VERSION
I0117 13:46:34.376] test-6724261826-master              Ready,SchedulingDisabled   <none>   16s   v1.17.2-beta.0
I0117 13:46:34.376] test-6724261826-minion-group-dj5b   Ready                      <none>   17s   v1.17.2-beta.0
I0117 13:46:34.376] test-6724261826-minion-group-g7rk   Ready                      <none>   16s   v1.17.2-beta.0
I0117 13:46:34.376] test-6724261826-minion-group-tqt1   Ready                      <none>   17s   v1.17.2-beta.0
I0117 13:46:34.714] Validate output:
I0117 13:46:35.008] NAME                 STATUS    MESSAGE             ERROR
I0117 13:46:35.008] controller-manager   Healthy   ok                  
I0117 13:46:35.008] etcd-1               Healthy   {"health":"true"}   
I0117 13:46:35.008] scheduler            Healthy   ok                  
I0117 13:46:35.008] etcd-0               Healthy   {"health":"true"}   
I0117 13:46:35.014] Cluster validation succeeded
W0117 13:46:35.114] Done, listing cluster services:
... skipping 96 lines ...
W0117 13:47:05.973] Using master: test-6724261826-master (external IP: 35.233.179.176; internal IP: (not set))
I0117 13:47:07.207] Jan 17 13:47:07.207: INFO: Fetching cloud provider for "gce"
I0117 13:47:07.207] I0117 13:47:07.207010    6706 test_context.go:419] Tolerating taints "node-role.kubernetes.io/master" when considering if nodes are ready
I0117 13:47:07.208] I0117 13:47:07.207685    6706 gce.go:860] Using DefaultTokenSource &oauth2.reuseTokenSource{new:jwt.jwtSource{ctx:(*context.emptyCtx)(0xc0000f0010), conf:(*jwt.Config)(0xc001b070e0)}, mu:sync.Mutex{state:0, sema:0x0}, t:(*oauth2.Token)(nil)}
I0117 13:47:07.292] W0117 13:47:07.291871    6706 gce.go:460] No network name or URL specified.
I0117 13:47:07.292] I0117 13:47:07.292055    6706 e2e.go:109] Starting e2e run "6ef7406f-59be-433c-8277-977d94230327" on Ginkgo node 1
I0117 13:47:07.306] {"msg":"Test Suite starting","total":4,"completed":0,"skipped":0,"failed":0}
I0117 13:47:07.306] Running Suite: Kubernetes e2e suite
I0117 13:47:07.306] ===================================
I0117 13:47:07.306] Random Seed: 1579268825 - Will randomize all specs
I0117 13:47:07.307] Will run 4 of 4843 specs
I0117 13:47:07.307] 
I0117 13:47:12.435] Jan 17 13:47:12.431: INFO: cluster-master-image: cos-77-12371-89-0
I0117 13:47:12.436] Jan 17 13:47:12.431: INFO: cluster-node-image: cos-77-12371-89-0
I0117 13:47:12.436] Jan 17 13:47:12.431: INFO: >>> kubeConfig: /workspace/.kube/config
I0117 13:47:12.437] Jan 17 13:47:12.436: INFO: Waiting up to 30m0s for all (but 0) nodes to be schedulable
I0117 13:47:12.614] Jan 17 13:47:12.611: INFO: Waiting up to 10m0s for all pods (need at least 8) in namespace 'kube-system' to be running and ready
I0117 13:47:12.848] Jan 17 13:47:12.846: INFO: The status of Pod etcd-empty-dir-cleanup-test-6724261826-master is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
I0117 13:47:12.849] Jan 17 13:47:12.846: INFO: 26 / 27 pods in namespace 'kube-system' are running and ready (0 seconds elapsed)
I0117 13:47:12.851] Jan 17 13:47:12.846: INFO: expected 9 pod replicas in namespace 'kube-system', 9 are Running and Ready.
I0117 13:47:12.852] Jan 17 13:47:12.846: INFO: POD                                            NODE                    PHASE    GRACE  CONDITIONS
I0117 13:47:12.853] Jan 17 13:47:12.846: INFO: etcd-empty-dir-cleanup-test-6724261826-master  test-6724261826-master  Pending         []
I0117 13:47:12.855] Jan 17 13:47:12.846: INFO: 
I0117 13:47:15.007] Jan 17 13:47:15.004: INFO: The status of Pod etcd-empty-dir-cleanup-test-6724261826-master is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
I0117 13:47:15.009] Jan 17 13:47:15.004: INFO: The status of Pod etcd-server-events-test-6724261826-master is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
I0117 13:47:15.009] Jan 17 13:47:15.004: INFO: 26 / 28 pods in namespace 'kube-system' are running and ready (2 seconds elapsed)
I0117 13:47:15.010] Jan 17 13:47:15.004: INFO: expected 9 pod replicas in namespace 'kube-system', 9 are Running and Ready.
I0117 13:47:15.010] Jan 17 13:47:15.004: INFO: POD                                            NODE                    PHASE    GRACE  CONDITIONS
I0117 13:47:15.013] Jan 17 13:47:15.004: INFO: etcd-empty-dir-cleanup-test-6724261826-master  test-6724261826-master  Pending         []
I0117 13:47:15.013] Jan 17 13:47:15.004: INFO: etcd-server-events-test-6724261826-master      test-6724261826-master  Pending         []
I0117 13:47:15.014] Jan 17 13:47:15.004: INFO: 
I0117 13:47:16.994] Jan 17 13:47:16.994: INFO: The status of Pod etcd-empty-dir-cleanup-test-6724261826-master is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
I0117 13:47:16.995] Jan 17 13:47:16.994: INFO: The status of Pod etcd-server-events-test-6724261826-master is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
I0117 13:47:16.996] Jan 17 13:47:16.994: INFO: 26 / 28 pods in namespace 'kube-system' are running and ready (4 seconds elapsed)
I0117 13:47:16.996] Jan 17 13:47:16.994: INFO: expected 9 pod replicas in namespace 'kube-system', 9 are Running and Ready.
I0117 13:47:16.997] Jan 17 13:47:16.994: INFO: POD                                            NODE                    PHASE    GRACE  CONDITIONS
I0117 13:47:16.997] Jan 17 13:47:16.994: INFO: etcd-empty-dir-cleanup-test-6724261826-master  test-6724261826-master  Pending         []
I0117 13:47:16.998] Jan 17 13:47:16.994: INFO: etcd-server-events-test-6724261826-master      test-6724261826-master  Pending         []
I0117 13:47:16.998] Jan 17 13:47:16.994: INFO: 
I0117 13:47:19.001] Jan 17 13:47:19.000: INFO: The status of Pod etcd-empty-dir-cleanup-test-6724261826-master is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
I0117 13:47:19.025] Jan 17 13:47:19.000: INFO: The status of Pod etcd-server-events-test-6724261826-master is Pending (Ready = false), waiting for it to be either Running (with Ready = true) or Failed
I0117 13:47:19.026] Jan 17 13:47:19.000: INFO: 26 / 28 pods in namespace 'kube-system' are running and ready (6 seconds elapsed)
I0117 13:47:19.026] Jan 17 13:47:19.000: INFO: expected 9 pod replicas in namespace 'kube-system', 9 are Running and Ready.
I0117 13:47:19.027] Jan 17 13:47:19.000: INFO: POD                                            NODE                    PHASE    GRACE  CONDITIONS
I0117 13:47:19.027] Jan 17 13:47:19.000: INFO: etcd-empty-dir-cleanup-test-6724261826-master  test-6724261826-master  Pending         []
I0117 13:47:19.027] Jan 17 13:47:19.000: INFO: etcd-server-events-test-6724261826-master      test-6724261826-master  Pending         []
I0117 13:47:19.028] Jan 17 13:47:19.000: INFO: 
... skipping 38 lines ...
I0117 13:47:27.487] Jan 17 13:47:27.486: INFO: Running '/workspace/kubernetes/platforms/linux/amd64/kubectl --server=https://35.233.179.176 --kubeconfig=/workspace/.kube/config create -f - --namespace=ingress-2199'
I0117 13:47:27.914] Jan 17 13:47:27.914: INFO: stderr: ""
I0117 13:47:27.914] Jan 17 13:47:27.914: INFO: stdout: "service/echoheaders-https created\n"
I0117 13:47:27.915] Jan 17 13:47:27.914: INFO: Parsing ingress from test/e2e/testing-manifests/ingress/pre-shared-cert/ing.yaml
I0117 13:47:27.916] Jan 17 13:47:27.915: INFO: creating pre-shared-cert ingress
I0117 13:47:27.959] STEP: Test that ingress works with the pre-shared certificate
I0117 13:47:28.000] Jan 17 13:47:28.000: INFO: Waiting for Ingress ingress-2199/pre-shared-cert to acquire IP, error: <nil>, ipOrNameList: []
I0117 13:47:38.066] Jan 17 13:47:38.065: INFO: Waiting for Ingress ingress-2199/pre-shared-cert to acquire IP, error: <nil>, ipOrNameList: []
I0117 13:47:48.043] Jan 17 13:47:48.043: INFO: Waiting for Ingress ingress-2199/pre-shared-cert to acquire IP, error: <nil>, ipOrNameList: []
I0117 13:47:58.043] Jan 17 13:47:58.043: INFO: Waiting for Ingress ingress-2199/pre-shared-cert to acquire IP, error: <nil>, ipOrNameList: []
I0117 13:48:08.043] Jan 17 13:48:08.042: INFO: Waiting for Ingress ingress-2199/pre-shared-cert to acquire IP, error: <nil>, ipOrNameList: []
I0117 13:48:18.043] Jan 17 13:48:18.043: INFO: Found address 35.244.189.128 for ingress ingress-2199/pre-shared-cert
I0117 13:48:18.207] Jan 17 13:48:18.207: INFO: host  path http://35.233.191.13:32592: reached
I0117 13:48:18.207] Jan 17 13:48:18.207: INFO: Testing route https://35.244.189.128/test host test.ingress.com with simple GET
I0117 13:48:18.209] Jan 17 13:48:18.209: INFO: host test.ingress.com path https://35.244.189.128/test: Get https://35.244.189.128/test: EOF unreachable
I0117 13:48:48.212] Jan 17 13:48:48.212: INFO: host test.ingress.com path https://35.244.189.128/test: Get https://35.244.189.128/test: EOF unreachable
I0117 13:49:18.213] Jan 17 13:4