This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: doc: deprecate azure blob disk feature
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2020-07-08 20:33
Elapsed1h30m
Revisionf007c68ae9b5516ee4f82bef7279a8a880f780f2
Refs 92905
links{u'resultstore': {u'url': u'https://source.cloud.google.com/results/invocations/b3ee7da7-4873-4dd6-b6c6-b8d8ce6d5c74/targets/test'}}
resultstorehttps://source.cloud.google.com/results/invocations/b3ee7da7-4873-4dd6-b6c6-b8d8ce6d5c74/targets/test
job-versionv1.19.0-beta.2.794+c5ed34bb926287
revisionv1.19.0-beta.2.794+c5ed34bb926287

Test Failures


Up 42m16s

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\": \"VMStartTimedOut\",\r\n        \"message\": \"VM 'k8s-agentpool1-33535354-vmss_0' did not start in the allotted time. The VM may still start successfully. Please check the power state later.\"\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 148 lines ...
ssh key file /root/.ssh/id_rsa does not exist. Exiting.
2020/07/08 21:56:32 process.go:155: Step 'bash -c /root/tmp958379546/win-ci-logs-collector.sh kubetest-5e1c5782-c15a-11ea-9d6d-3601aaae5947.westus2.cloudapp.azure.com /root/tmp958379546 /root/.ssh/id_rsa' finished in 22.740403ms
2020/07/08 21:56:32 aksengine.go:1155: Deleting resource group: kubetest-5e1c5782-c15a-11ea-9d6d-3601aaae5947.
2020/07/08 22:04:07 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2020/07/08 22:04:07 process.go:153: Running: bash -c . hack/lib/version.sh && KUBE_ROOT=. kube::version::get_version_vars && echo "${KUBE_GIT_VERSION-}"
2020/07/08 22:04:10 process.go:155: Step 'bash -c . hack/lib/version.sh && KUBE_ROOT=. kube::version::get_version_vars && echo "${KUBE_GIT_VERSION-}"' finished in 2.960475906s
2020/07/08 22:04:10 main.go:312: 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\": \"VMStartTimedOut\",\r\n        \"message\": \"VM 'k8s-agentpool1-33535354-vmss_0' did not start in the allotted time. The VM may still start successfully. Please check the power state later.\"\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 ...