This job view page is being replaced by Spyglass soon. Check out the new job view.
PRchewong: test: use `WaitForFirstConsumer` for in-tree storage driver
ResultFAILURE
Tests 1 failed / 4 succeeded
Started2021-04-08 21:10
Elapsed43m58s
Revision5c337c471c009305f4ad72f2d35e489f26eebafe
Refs 774
job-versionv1.22.0-alpha.0.35+f7e5c6e7d30f0e
kubetest-version
revisionv1.22.0-alpha.0.35+f7e5c6e7d30f0e

Test Failures


Up 27m24s

error creating cluster: cannot deploy: cannot get the create deployment future response: Code="DeploymentFailed" Message="At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details." Details=[{"code":"Conflict","message":"{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      {\r\n        \"code\": \"VMAgentStatusCommunicationError\",\r\n        \"message\": \"VM 'k8s-master-11118344-0' has not reported status for VM agent or extensions. Verify that the OS is up and healthy, the VM has a running VM agent, and that it can establish outbound connections to Azure storage. Please refer to https://aka.ms/vmextensionlinuxtroubleshoot for additional VM agent troubleshooting information.\"\r\n      }\r\n    ]\r\n  }\r\n}"},{"code":"Conflict","message":"{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      {\r\n        \"code\": \"VMAgentStatusCommunicationError\",\r\n        \"message\": \"VM 'k8s-master-11118344-0' has not reported status for VM agent or extensions. Verify that the OS is up and healthy, the VM has a running VM agent, and that it can establish outbound connections to Azure storage. Please refer to https://aka.ms/vmextensionlinuxtroubleshoot for additional VM agent troubleshooting information.\"\r\n      }\r\n    ]\r\n  }\r\n}"}]
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 4 Passed Tests

Error lines from build-log.txt

... skipping 35 lines ...
2021/04/08 21:37:37 aksengine_helpers.go:425: downloading /root/tmp266523804/log-dump-daemonset.yaml from https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/hack/log-dump/log-dump-daemonset.yaml
2021/04/08 21:37:37 util.go:68: curl https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/hack/log-dump/log-dump-daemonset.yaml
2021/04/08 21:37:37 process.go:153: Running: bash -c /root/tmp266523804/log-dump.sh
Installing log-dump-daemonset.yaml via kubectl
Unable to connect to the server: dial tcp 20.72.92.251:443: i/o timeout
Uninstalling log-dump-daemonset.yaml via kubectl
error: unable to recognize "/root/tmp266523804/log-dump-daemonset.yaml": Get "https://kubetest-iz8dymyl.eastus2.cloudapp.azure.com/api?timeout=32s": dial tcp 20.72.92.251:443: i/o timeout
2021/04/08 21:38:37 process.go:155: Step 'bash -c /root/tmp266523804/log-dump.sh' finished in 1m0.447886282s
2021/04/08 21:38:37 aksengine_helpers.go:425: downloading /root/tmp266523804/win-ci-logs-collector.sh from https://raw.githubusercontent.com/kubernetes-sigs/windows-testing/master/scripts/win-ci-logs-collector.sh
2021/04/08 21:38:37 util.go:68: curl https://raw.githubusercontent.com/kubernetes-sigs/windows-testing/master/scripts/win-ci-logs-collector.sh
2021/04/08 21:38:37 process.go:153: Running: chmod +x /root/tmp266523804/win-ci-logs-collector.sh
2021/04/08 21:38:37 process.go:155: Step 'chmod +x /root/tmp266523804/win-ci-logs-collector.sh' finished in 2.29251ms
2021/04/08 21:38:37 process.go:153: Running: bash -c /root/tmp266523804/win-ci-logs-collector.sh kubetest-iz8dymyl.eastus2.cloudapp.azure.com /root/tmp266523804 /root/.ssh/id_rsa
ssh key file /root/.ssh/id_rsa does not exist. Exiting.
2021/04/08 21:38:37 process.go:155: Step 'bash -c /root/tmp266523804/win-ci-logs-collector.sh kubetest-iz8dymyl.eastus2.cloudapp.azure.com /root/tmp266523804 /root/.ssh/id_rsa' finished in 7.474209ms
2021/04/08 21:38:37 aksengine.go:1134: Deleting resource group: kubetest-iz8dymyl.
2021/04/08 21:53:38 aksengine_helpers.go:326: Warning: failed to delete resource group "kubetest-iz8dymyl" with error Future#WaitForCompletion: context has been cancelled: StatusCode=202 -- Original Error: context deadline exceeded
2021/04/08 21:53:38 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2021/04/08 21:53:38 process.go:153: Running: bash -c . hack/lib/version.sh && KUBE_ROOT=. kube::version::get_version_vars && echo "${KUBE_GIT_VERSION-}"
2021/04/08 21:53:41 process.go:155: Step 'bash -c . hack/lib/version.sh && KUBE_ROOT=. kube::version::get_version_vars && echo "${KUBE_GIT_VERSION-}"' finished in 2.637863985s
2021/04/08 21:53:41 main.go:327: Something went wrong: starting e2e cluster: error creating cluster: cannot deploy: cannot get the create deployment future response: Code="DeploymentFailed" Message="At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details." Details=[{"code":"Conflict","message":"{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      {\r\n        \"code\": \"VMAgentStatusCommunicationError\",\r\n        \"message\": \"VM 'k8s-master-11118344-0' has not reported status for VM agent or extensions. Verify that the OS is up and healthy, the VM has a running VM agent, and that it can establish outbound connections to Azure storage. Please refer to https://aka.ms/vmextensionlinuxtroubleshoot for additional VM agent troubleshooting information.\"\r\n      }\r\n    ]\r\n  }\r\n}"},{"code":"Conflict","message":"{\r\n  \"status\": \"Failed\",\r\n  \"error\": {\r\n    \"code\": \"ResourceDeploymentFailure\",\r\n    \"message\": \"The resource operation completed with terminal provisioning state 'Failed'.\",\r\n    \"details\": [\r\n      {\r\n        \"code\": \"VMAgentStatusCommunicationError\",\r\n        \"message\": \"VM 'k8s-master-11118344-0' has not reported status for VM agent or extensions. Verify that the OS is up and healthy, the VM has a running VM agent, and that it can establish outbound connections to Azure storage. Please refer to https://aka.ms/vmextensionlinuxtroubleshoot for additional VM agent troubleshooting information.\"\r\n      }\r\n    ]\r\n  }\r\n}"}]
+ EXIT_VALUE=1
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
Cleaning up after docker
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
... skipping 3 lines ...