This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: Automated cherry pick of #94340: Update max data disk count with new instance types
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2020-11-17 11:57
Elapsed1h1m
Revisionb241841e55dd5cbfb79dc876daca3da2d7722431
Refs 96412
job-versionv1.17.15-rc.0.5+e8de6468b23aca
revisionv1.17.15-rc.0.5+e8de6468b23aca

Test Failures


Up 28m21s

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\": \"VMExtensionProvisioningError\",\r\n        \"message\": \"Multiple VM extensions failed to be provisioned on the VM. Please see the VM extension instance view for other failures. The first extension failed due to the error: VM 'k8s-agentpool1-65840118-vmss_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 5 Passed Tests

Error lines from build-log.txt

... skipping 153 lines ...
2020/11/17 12:44:01 process.go:153: Running: chmod +x /root/tmp200259111/win-ci-logs-collector.sh
2020/11/17 12:44:01 process.go:155: Step 'chmod +x /root/tmp200259111/win-ci-logs-collector.sh' finished in 1.191175ms
2020/11/17 12:44:01 process.go:153: Running: bash -c /root/tmp200259111/win-ci-logs-collector.sh kubetest-15240af8-28cc-11eb-92a6-3eb67127350d.westus2.cloudapp.azure.com /root/tmp200259111 /root/.ssh/id_rsa
ssh key file /root/.ssh/id_rsa does not exist. Exiting.
2020/11/17 12:44:01 process.go:155: Step 'bash -c /root/tmp200259111/win-ci-logs-collector.sh kubetest-15240af8-28cc-11eb-92a6-3eb67127350d.westus2.cloudapp.azure.com /root/tmp200259111 /root/.ssh/id_rsa' finished in 5.96934ms
2020/11/17 12:44:01 aksengine.go:1128: Deleting resource group: kubetest-15240af8-28cc-11eb-92a6-3eb67127350d.
2020/11/17 12:59:02 aksengine_helpers.go:323: Warning: failed to delete resource group "kubetest-15240af8-28cc-11eb-92a6-3eb67127350d" with error Future#WaitForCompletion: context has been cancelled: StatusCode=202 -- Original Error: context deadline exceeded
2020/11/17 12:59:02 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2020/11/17 12:59:02 process.go:153: Running: bash -c . hack/lib/version.sh && KUBE_ROOT=. kube::version::get_version_vars && echo "${KUBE_GIT_VERSION-}"
2020/11/17 12:59:05 process.go:155: Step 'bash -c . hack/lib/version.sh && KUBE_ROOT=. kube::version::get_version_vars && echo "${KUBE_GIT_VERSION-}"' finished in 2.409033626s
2020/11/17 12:59:05 main.go:316: 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\": \"VMExtensionProvisioningError\",\r\n        \"message\": \"Multiple VM extensions failed to be provisioned on the VM. Please see the VM extension instance view for other failures. The first extension failed due to the error: VM 'k8s-agentpool1-65840118-vmss_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
0d7e80bcd7b3
... skipping 4 lines ...