cloud-provider-azure-slow-vmss #1532266305732743168
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 1 failed / 7 succeeded |
| Started | |
| Elapsed | 33m9s |
| Revision | release-1.23 |
| job-version | v1.23.8-rc.0.3+9c77bfb6f557b7 |
| kubetest-version | |
| revision | v1.23.8-rc.0.3+9c77bfb6f557b7 |
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\": \"AllocationFailed\",\r\n \"message\": \"The VM allocation failed due to an internal error. Please retry later or try deploying to a different location.\"\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\": \"AllocationFailed\",\r\n \"message\": \"The VM allocation failed due to an internal error. Please retry later or try deploying to a different location.\"\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\": \"AllocationFailed\",\r\n \"message\": \"The VM allocation failed due to an internal error. Please retry later or try deploying to a different location.\"\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\": \"AllocationFailed\",\r\n \"message\": \"The VM allocation failed due to an internal error. Please retry later or try deploying to a different location.\"\r\n }\r\n ]\r\n }\r\n}"}]
from junit_runner.xml
Filter through log files
kubetest Build
kubetest Deferred TearDown
kubetest DumpClusterLogs (--up failed)
kubetest GetDeployer
kubetest Prepare
kubetest TearDown Previous
kubetest Timeout
... skipping 75 lines ... 2022/06/02 08:11:46 aksengine_helpers.go:426: downloading /root/tmp1139048444/log-dump-daemonset.yaml from https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/hack/log-dump/log-dump-daemonset.yaml 2022/06/02 08:11:46 util.go:71: curl https://raw.githubusercontent.com/kubernetes-sigs/cloud-provider-azure/master/hack/log-dump/log-dump-daemonset.yaml 2022/06/02 08:11:46 process.go:153: Running: bash -c /root/tmp1139048444/log-dump.sh Installing log-dump-daemonset.yaml via kubectl Unable to connect to the server: dial tcp 20.1.217.171:443: i/o timeout Uninstalling log-dump-daemonset.yaml via kubectl error: unable to recognize "/root/tmp1139048444/log-dump-daemonset.yaml": Get "https://kubetest-0pmlpcfq.eastus2.cloudapp.azure.com/api?timeout=32s": dial tcp 20.1.217.171:443: i/o timeout 2022/06/02 08:12:47 process.go:155: Step 'bash -c /root/tmp1139048444/log-dump.sh' finished in 1m0.578641286s 2022/06/02 08:12:47 aksengine_helpers.go:426: downloading /root/tmp1139048444/win-ci-logs-collector.sh from https://raw.githubusercontent.com/kubernetes-sigs/windows-testing/master/scripts/win-ci-logs-collector.sh 2022/06/02 08:12:47 util.go:71: curl https://raw.githubusercontent.com/kubernetes-sigs/windows-testing/master/scripts/win-ci-logs-collector.sh 2022/06/02 08:12:47 process.go:153: Running: chmod +x /root/tmp1139048444/win-ci-logs-collector.sh 2022/06/02 08:12:47 process.go:155: Step 'chmod +x /root/tmp1139048444/win-ci-logs-collector.sh' finished in 1.271542ms 2022/06/02 08:12:47 process.go:153: Running: bash -c /root/tmp1139048444/win-ci-logs-collector.sh kubetest-0pmlpcfq.eastus2.cloudapp.azure.com /root/tmp1139048444 /root/.ssh/id_rsa ssh key file /root/.ssh/id_rsa does not exist. Exiting. 2022/06/02 08:12:47 process.go:155: Step 'bash -c /root/tmp1139048444/win-ci-logs-collector.sh kubetest-0pmlpcfq.eastus2.cloudapp.azure.com /root/tmp1139048444 /root/.ssh/id_rsa' finished in 3.847282ms 2022/06/02 08:12:47 aksengine.go:1141: Deleting resource group: kubetest-0pmlpcfq. 2022/06/02 08:17:04 process.go:96: Saved XML output to /logs/artifacts/junit_runner.xml. 2022/06/02 08:17:04 process.go:153: Running: bash -c . hack/lib/version.sh && KUBE_ROOT=. kube::version::get_version_vars && echo "${KUBE_GIT_VERSION-}" 2022/06/02 08:17:06 process.go:155: Step 'bash -c . hack/lib/version.sh && KUBE_ROOT=. kube::version::get_version_vars && echo "${KUBE_GIT_VERSION-}"' finished in 1.571764001s 2022/06/02 08:17:06 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\": \"AllocationFailed\",\r\n \"message\": \"The VM allocation failed due to an internal error. Please retry later or try deploying to a different location.\"\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\": \"AllocationFailed\",\r\n \"message\": \"The VM allocation failed due to an internal error. Please retry later or try deploying to a different location.\"\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\": \"AllocationFailed\",\r\n \"message\": \"The VM allocation failed due to an internal error. Please retry later or try deploying to a different location.\"\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\": \"AllocationFailed\",\r\n \"message\": \"The VM allocation failed due to an internal error. Please retry later or try deploying to a different location.\"\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 ...