This job view page is being replaced by Spyglass soon. Check out the new job view.
PRsunpa93: [V2] fix: CRI recovery should not overwrite existing values
ResultFAILURE
Tests 1 failed / 7 succeeded
Started2022-09-20 16:31
Elapsed1h17m
Revision42b3f3de3dca6dfef6983664bef688a3b8230db6
Refs 1518
job-versionv1.26.0-alpha.0.694+9c9b29032f76e3
kubetest-versionv20220916-c3af09ab20
revisionv1.26.0-alpha.0.694+9c9b29032f76e3

Test Failures


kubetest Up 50m32s

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\": \"VM has reported a failure when processing extension 'vmssCSE'. Error message: \\\"Command execution finished, but failed because it returned a non-zero exit code of: '1'\\\"\\r\\n\\r\\nMore information on troubleshooting is available at https://aka.ms/VMExtensionCSEWindowsTroubleshoot \"\r\n      }\r\n    ]\r\n  }\r\n}"}]
				from junit_runner.xml

Filter through log files | View test history on testgrid


Show 7 Passed Tests

Error lines from build-log.txt

... skipping 113 lines ...
ssh_exchange_identification: Connection closed by remote host
2022/09/20 17:41:56 process.go:155: Step 'bash -c /root/tmp2911064092/win-ci-logs-collector.sh kubetest-rpo2st6c.westus2.cloudapp.azure.com /root/tmp2911064092 /etc/ssh-key-secret/ssh-private' finished in 19m39.457573156s
2022/09/20 17:41:56 aksengine.go:1141: Deleting resource group: kubetest-rpo2st6c.
2022/09/20 17:48:00 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml.
2022/09/20 17:48:00 process.go:153: Running: bash -c . hack/lib/version.sh && KUBE_ROOT=. kube::version::get_version_vars && echo "${KUBE_GIT_VERSION-}"
2022/09/20 17:48:02 process.go:155: Step 'bash -c . hack/lib/version.sh && KUBE_ROOT=. kube::version::get_version_vars && echo "${KUBE_GIT_VERSION-}"' finished in 1.885375894s
2022/09/20 17:48:02 main.go:331: 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\": \"VM has reported a failure when processing extension 'vmssCSE'. Error message: \\\"Command execution finished, but failed because it returned a non-zero exit code of: '1'\\\"\\r\\n\\r\\nMore information on troubleshooting is available at https://aka.ms/VMExtensionCSEWindowsTroubleshoot \"\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 ...