This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 18 failed / 175 succeeded
Started2020-01-13 17:25
Elapsed8h11m
Revision
Buildergke-prow-default-pool-cf4891d4-5bng
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/a39cc15c-5681-409c-898f-62d7d12057ff/targets/test'}}
pod8dd24950-3629-11ea-9fef-d200904e1a96
resultstorehttps://source.cloud.google.com/results/invocations/a39cc15c-5681-409c-898f-62d7d12057ff/targets/test
infra-commitb3462c342
job-versionv1.16.5-beta.1.51+e7f962ba86f4ce
master_os_imagecos-77-12371-89-0
node_os_imagecos-73-11647-163-0
pod8dd24950-3629-11ea-9fef-d200904e1a96
revisionv1.16.5-beta.1.51+e7f962ba86f4ce

Test Failures


Kubernetes e2e suite [k8s.io] [sig-cloud-provider-gcp] Upgrade [Feature:Upgrade] master upgrade should maintain a functioning cluster [Feature:MasterUpgrade] 17m48s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[k8s\.io\]\s\[sig\-cloud\-provider\-gcp\]\sUpgrade\s\[Feature\:Upgrade\]\smaster\supgrade\sshould\smaintain\sa\sfunctioning\scluster\s\[Feature\:MasterUpgrade\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/cloud/gcp/cluster_upgrade.go:91
Jan 13 17:42:54.736: Unexpected error:
    <*errors.errorString | 0xc002ee0700>: {
        s: "error running /workspace/kubernetes_skew/cluster/gce/upgrade.sh [-M v1.17.1-beta.0.52+d224476cd0730b]; got error exit status 1, stdout \"Fetching the previously installed CoreDNS version\\n\\n***WARNING***\\nUpgrading Kubernetes with this script might result in an upgrade to a new etcd version.\\nSome etcd version upgrades, such as 3.0.x to 3.1.x, DO NOT offer a downgrade path.\\nTo pin the etcd version to your current one (e.g. v3.0.17), set the following variables\\nbefore running this script:\\n\\n# example: pin to etcd v3.0.17\\nexport ETCD_IMAGE=3.0.17\\nexport ETCD_VERSION=3.0.17\\n\\nAlternatively, if you choose to allow an etcd upgrade that doesn't support downgrade,\\nyou might still be able to downgrade Kubernetes by pinning to the newer etcd version.\\nIn all cases, it is strongly recommended to have an etcd backup before upgrading.\\n\\n== Pre-Upgrade Node OS and Kubelet Versions ==\\nname: \\\"bootstrap-e2e-master\\\", osImage: \\\"Container-Optimized OS from Google\\\", kubeletVersion: \\\"v1.16.5-beta.1.51+e7f962ba86f4ce\\\"\\nname: \\\"bootstrap-e2e-minion-group-l4kv\\\", osImage: \\\"Container-Optimized OS from Google\\\", kubeletVersion: \\\"v1.16.5-beta.1.51+e7f962ba86f4ce\\\"\\nname: \\\"bootstrap-e2e-minion-group-rt3j\\\", osImage: \\\"Container-Optimized OS from Google\\\", kubeletVersion: \\\"v1.16.5-beta.1.51+e7f962ba86f4ce\\\"\\nname: \\\"bootstrap-e2e-minion-group-xdpk\\\", osImage: \\\"Container-Optimized OS from Google\\\", kubeletVersion: \\\"v1.16.5-beta.1.51+e7f962ba86f4ce\\\"\\nFound subnet for region us-west1 in network bootstrap-e2e: bootstrap-e2e\\n== Upgrading master to 'https://storage.googleapis.com/kubernetes-release-dev/ci/v1.17.1-beta.0.52+d224476cd0730b/kubernetes-server-linux-amd64.tar.gz'. Do not interrupt, deleting master instance. ==\\n== Upgrading master environment variables. ==\\n== Waiting for new master to respond to API requests ==\\n.........................== Done ==\\nWaiting for CoreDNS to update\\nFetching the latest installed CoreDNS version\\n== Downloading the CoreDNS migration tool ==\\n== Upgrading the CoreDNS ConfigMap ==\\nconfigmap/coredns configured\\n== The CoreDNS Config has been updated ==\\n== Validating cluster post-upgrade ==\\nValidating gce cluster, MULTIZONE=\\nFound 4 node(s).\\nNAME                              STATUS                     ROLES    AGE     VERSION\\nbootstrap-e2e-master              Ready,SchedulingDisabled   <none>   9m44s   v1.17.1-beta.0.52+d224476cd0730b\\nbootstrap-e2e-minion-group-l4kv   Ready                      <none>   9m38s   v1.16.5-beta.1.51+e7f962ba86f4ce\\nbootstrap-e2e-minion-group-rt3j   Ready                      <none>   9m37s   v1.16.5-beta.1.51+e7f962ba86f4ce\\nbootstrap-e2e-minion-group-xdpk   Ready                      <none>   9m37s   v1.16.5-beta.1.51+e7f962ba86f4ce\\nValidate output:\\nNAME                 STATUS    MESSAGE             ERROR\\netcd-1               Healthy   {\\\"health\\\":\\\"true\\\"}   \\nscheduler            Healthy   ok                  \\netcd-0               Healthy   {\\\"health\\\":\\\"true\\\"}   \\ncontroller-manager   Healthy   ok                  \\n\\x1b[0;32mCluster validation succeeded\\x1b[0m\\n== Post-Upgrade Node OS and Kubelet Versions ==\\nname: \\\"bootstrap-e2e-master\\\", osImage: \\\"Container-Optimized OS from Google\\\", kubeletVersion: \\\"v1.17.1-beta.0.52+d224476cd0730b\\\"\\nname: \\\"bootstrap-e2e-minion-group-l4kv\\\", osImage: \\\"Container-Optimized OS from Google\\\", kubeletVersion: \\\"v1.16.5-beta.1.51+e7f962ba86f4ce\\\"\\nname: \\\"bootstrap-e2e-minion-group-rt3j\\\", osImage: \\\"Container-Optimized OS from Google\\\", kubeletVersion: \\\"v1.16.5-beta.1.51+e7f962ba86f4ce\\\"\\nname: \\\"bootstrap-e2e-minion-group-xdpk\\\", osImage: \\\"Container-Optimized OS from Google\\\", kubeletVersion: \\\"v1.16.5-beta.1.51+e7f962ba86f4ce\\\"\\n\", stderr \"Project: gce-up-c1-3-g1-4-up-clu\\nNetwork Project: gce-up-c1-3-g1-4-up-clu\\nZone: us-west1-b\\nINSTANCE_GROUPS=bootstrap-e2e-minion-group\\nNODE_NAMES=bootstrap-e2e-minion-group-l4kv bootstrap-e2e-minion-group-rt3j bootstrap-e2e-minion-group-xdpk\\nTrying to find master named 'bootstrap-e2e-master'\\nLooking for address 'bootstrap-e2e-master-ip'\\nUsing master: bootstrap-e2e-master (external IP: 35.247.22.167; internal IP: (not set))\\nDeleted [https://www.googleapis.com/compute/v1/projects/gce-up-c1-3-g1-4-up-clu/zones/us-west1-b/instances/bootstrap-e2e-master].\\nWARNING: You have selected a disk size of under [200GB]. This may result in poor I/O performance. For more information, see: https://developers.google.com/compute/docs/disks#performance.\\nCreated [https://www.googleapis.com/compute/v1/projects/gce-up-c1-3-g1-4-up-clu/zones/us-west1-b/instances/bootstrap-e2e-master].\\nWARNING: Some requests generated warnings:\\n - Disk size: '20 GB' is larger than image size: '10 GB'. You might need to resize the root repartition manually if the operating system does not support automatic resizing. See https://cloud.google.com/compute/docs/disks/add-persistent-disk#resize_pd for details.\\n - The resource 'projects/cos-cloud/global/images/cos-77-12371-89-0' is deprecated. A suggested replacement is 'projects/cos-cloud/global/images/cos-77-12371-114-0'.\\n\\nNAME                  ZONE        MACHINE_TYPE   PREEMPTIBLE  INTERNAL_IP  EXTERNAL_IP    STATUS\\nbootstrap-e2e-master  us-west1-b  n1-standard-1               10.138.0.6   35.247.22.167  RUNNING\\nWarning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply\\nProject: gce-up-c1-3-g1-4-up-clu\\nNetwork Project: gce-up-c1-3-g1-4-up-clu\\nZone: us-west1-b\\n/workspace/kubernetes_skew/cluster/gce/upgrade.sh: line 452: download_dir: unbound variable\\n\"",
    }
    error running /workspace/kubernetes_skew/cluster/gce/upgrade.sh [-M v1.17.1-beta.0.52+d224476cd0730b]; got error exit status 1, stdout "Fetching the previously installed CoreDNS version\n\n***WARNING***\nUpgrading Kubernetes with this script might result in an upgrade to a new etcd version.\nSome etcd version upgrades, such as 3.0.x to 3.1.x, DO NOT offer a downgrade path.\nTo pin the etcd version to your current one (e.g. v3.0.17), set the following variables\nbefore running this script:\n\n# example: pin to etcd v3.0.17\nexport ETCD_IMAGE=3.0.17\nexport ETCD_VERSION=3.0.17\n\nAlternatively, if you choose to allow an etcd upgrade that doesn't support downgrade,\nyou might still be able to downgrade Kubernetes by pinning to the newer etcd version.\nIn all cases, it is strongly recommended to have an etcd backup before upgrading.\n\n== Pre-Upgrade Node OS and Kubelet Versions ==\nname: \"bootstrap-e2e-master\", osImage: \"Container-Optimized OS from Google\", kubeletVersion: \"v1.16.5-beta.1.51+e7f962ba86f4ce\"\nname: \"bootstrap-e2e-minion-group-l4kv\", osImage: \"Container-Optimized OS from Google\", kubeletVersion: \"v1.16.5-beta.1.51+e7f962ba86f4ce\"\nname: \"bootstrap-e2e-minion-group-rt3j\", osImage: \"Container-Optimized OS from Google\", kubeletVersion: \"v1.16.5-beta.1.51+e7f962ba86f4ce\"\nname: \"bootstrap-e2e-minion-group-xdpk\", osImage: \"Container-Optimized OS from Google\", kubeletVersion: \"v1.16.5-beta.1.51+e7f962ba86f4ce\"\nFound subnet for region us-west1 in network bootstrap-e2e: bootstrap-e2e\n== Upgrading master to 'https://storage.googleapis.com/kubernetes-release-dev/ci/v1.17.1-beta.0.52+d224476cd0730b/kubernetes-server-linux-amd64.tar.gz'. Do not interrupt, deleting master instance. ==\n== Upgrading master environment variables. ==\n== Waiting for new master to respond to API requests ==\n.........................== Done ==\nWaiting for CoreDNS to update\nFetching the latest installed CoreDNS version\n== Downloading the CoreDNS migration tool ==\n== Upgrading the CoreDNS ConfigMap ==\nconfigmap/coredns configured\n== The CoreDNS Config has been updated ==\n== Validating cluster post-upgrade ==\nValidating gce cluster, MULTIZONE=\nFound 4 node(s).\nNAME                              STATUS                     ROLES    AGE     VERSION\nbootstrap-e2e-master              Ready,SchedulingDisabled   <none>   9m44s   v1.17.1-beta.0.52+d224476cd0730b\nbootstrap-e2e-minion-group-l4kv   Ready                      <none>   9m38s   v1.16.5-beta.1.51+e7f962ba86f4ce\nbootstrap-e2e-minion-group-rt3j   Ready                      <none>   9m37s   v1.16.5-beta.1.51+e7f962ba86f4ce\nbootstrap-e2e-minion-group-xdpk   Ready                      <none>   9m37s   v1.16.5-beta.1.51+e7f962ba86f4ce\nValidate output:\nNAME                 STATUS    MESSAGE             ERROR\netcd-1               Healthy   {\"health\":\"true\"}   \nscheduler            Healthy   ok                  \netcd-0               Healthy   {\"health\":\"true\"}   \ncontroller-manager   Healthy   ok                  \n\x1b[0;32mCluster validation succeeded\x1b[0m\n== Post-Upgrade Node OS and Kubelet Versions ==\nname: \"bootstrap-e2e-master\", osImage: \"Container-Optimized OS from Google\", kubeletVersion: \"v1.17.1-beta.0.52+d224476cd0730b\"\nname: \"bootstrap-e2e-minion-group-l4kv\", osImage: \"Container-Optimized OS from Google\", kubeletVersion: \"v1.16.5-beta.1.51+e7f962ba86f4ce\"\nname: \"bootstrap-e2e-minion-group-rt3j\", osImage: \"Container-Optimized OS from Google\", kubeletVersion: \"v1.16.5-beta.1.51+e7f962ba86f4ce\"\nname: \"bootstrap-e2e-minion-group-xdpk\", osImage: \"Container-Optimized OS from Google\", kubeletVersion: \"v1.16.5-beta.1.51+e7f962ba86f4ce\"\n", stderr "Project: gce-up-c1-3-g1-4-up-clu\nNetwork Project: gce-up-c1-3-g1-4-up-clu\nZone: us-west1-b\nINSTANCE_GROUPS=bootstrap-e2e-minion-group\nNODE_NAMES=bootstrap-e2e-minion-group-l4kv bootstrap-e2e-minion-group-rt3j bootstrap-e2e-minion-group-xdpk\nTrying to find master named 'bootstrap-e2e-master'\nLooking for address 'bootstrap-e2e-master-ip'\nUsing master: bootstrap-e2e-master (external IP: 35.247.22.167; internal IP: (not set))\nDeleted [https://www.googleapis.com/compute/v1/projects/gce-up-c1-3-g1-4-up-clu/zones/us-west1-b/instances/bootstrap-e2e-master].\nWARNING: You have selected a disk size of under [200GB]. This may result in poor I/O performance. For more information, see: https://developers.google.com/compute/docs/disks#performance.\nCreated [https://www.googleapis.com/compute/v1/projects/gce-up-c1-3-g1-4-up-clu/zones/us-west1-b/instances/bootstrap-e2e-master].\nWARNING: Some requests generated warnings:\n - Disk size: '20 GB' is larger than image size: '10 GB'. You might need to resize the root repartition manually if the operating system does not support automatic resizing. See https://cloud.google.com/compute/docs/disks/add-persistent-disk#resize_pd for details.\n - The resource 'projects/cos-cloud/global/images/cos-77-12371-89-0' is deprecated. A suggested replacement is 'projects/cos-cloud/global/images/cos-77-12371-114-0'.\n\nNAME                  ZONE        MACHINE_TYPE   PREEMPTIBLE  INTERNAL_IP  EXTERNAL_IP    STATUS\nbootstrap-e2e-master  us-west1-b  n1-standard-1               10.138.0.6   35.247.22.167  RUNNING\nWarning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply\nProject: gce-up-c1-3-g1-4-up-clu\nNetwork Project: gce-up-c1-3-g1-4-up-clu\nZone: us-west1-b\n/workspace/kubernetes_skew/cluster/gce/upgrade.sh: line 452: download_dir: unbound variable\n"
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/cloud/gcp/cluster_upgrade.go:106
				
				Click to see stdout/stderrfrom junit_upgrade01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-apps] Daemon set [Serial] should not update pod when spec was updated and update strategy is OnDelete 15m17s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sDaemon\sset\s\[Serial\]\sshould\snot\supdate\spod\swhen\sspec\swas\supdated\sand\supdate\sstrategy\sis\sOnDelete$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:277
Jan 13 23:34:54.988: error waiting for daemon pod to start
Unexpected error:
    <*errors.errorString | 0xc0000d3000>: {
        s: "timed out waiting for the condition",
    }
    timed out waiting for the condition
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_set.go:288
				
				Click to see stdout/stderrfrom junit_01.xml

Find to mentions in log files | View test history on testgrid


Kubernetes e2e suite [sig-apps] Daemon set [Serial] should run and stop complex daemon [Conformance] 10m21s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sDaemon\sset\s\[Serial\]\sshould\srun\sand\sstop\scomplex\sdaemon\s\[Conformance\]$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:152
Jan 14 00:58:34.832: Couldn't delete ns: "daemonsets-469": namespace daemonsets-469 was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed (&errors.errorString{s:"namespace daemonsets-469 was not deleted with limit: timed out waiting for the condition, namespace is empty but is not yet removed"})
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/framework/framework.go:336
				
				Click to see stdout/stderrfrom junit_01.xml

Filter through log files | View test history on testgrid


Kubernetes e2e suite [sig-apps] DaemonRestart [Disruptive] Controller Manager should not create/delete replicas across restart 15m13s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=Kubernetes\se2e\ssuite\s\[sig\-apps\]\sDaemonRestart\s\[Disruptive\]\sController\sManager\sshould\snot\screate\/delete\sreplicas\sacross\srestart$'
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_restart.go:197
Jan 13 22:29:39.709: Unexpected error:
    <*errors.errorString | 0xc00389cba0>: {
        s: "Only 7 pods started out of 10",
    }
    Only 7 pods started out of 10
occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/apps/daemon_restart.go:212