This job view page is being replaced by Spyglass soon. Check out the new job view.
PRchewong: Revert "list vm instead of get when getting virtual machine"
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2020-01-14 22:56
Elapsed46m48s
Revision80c967ad69371a9338f7ad0abdd87fe5ca39d686
Refs 87210

No Test Failures!


Error lines from build-log.txt

... skipping 119 lines ...
2020/01/14 23:28:27 azure.go:674: Setting kubeconfig env variable: kubeconfig path: /root/aks875492841/kubeconfig/kubeconfig.westus2.json.
2020/01/14 23:28:27 azure.go:676: Creating resource group: kubetest-1e748be9-3721-11ea-839b-2e9f32609596.
2020/01/14 23:28:27 azure.go:678: Creating Azure resource group: kubetest-1e748be9-3721-11ea-839b-2e9f32609596 for cluster deployment.
2020/01/14 23:28:28 azure.go:683: Validating deployment ARM templates.
2020/01/14 23:28:31 azure.go:689: Deploying cluster kubetest-1e748be9-3721-11ea-839b-2e9f32609596 in resource group kubetest-1e748be9-3721-11ea-839b-2e9f32609596.
2020/01/14 23:33:35 azure.go:1049: Deleting resource group: kubetest-1e748be9-3721-11ea-839b-2e9f32609596.
2020/01/14 23:43:15 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\": \"VM has reported a failure when processing extension 'cse-master-0'. Error message: \\\"Enable failed: failed to execute command: command terminated with exit status=99\\n[stdout]\\nTue Jan 14 23:30:25 UTC 2020,k8s-master-37293710-0\\n\\n[stderr]\\n\\\"\\r\\n\\r\\nMore information on troubleshooting is available at https://aka.ms/VMExtensionCSELinuxTroubleshoot \"\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\": \"VMExtensionProvisioningError\",\r\n        \"message\": \"VM has reported a failure when processing extension 'cse-agent-1'. Error message: \\\"Enable failed: failed to execute command: command terminated with exit status=99\\n[stdout]\\nTue Jan 14 23:30:21 UTC 2020,k8s-agentpool1-37293710-1\\n\\n[stderr]\\n\\\"\\r\\n\\r\\nMore information on troubleshooting is available at https://aka.ms/VMExtensionCSELinuxTroubleshoot \"\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\": \"VMExtensionProvisioningError\",\r\n        \"message\": \"VM has reported a failure when processing extension 'cse-agent-0'. Error message: \\\"Enable failed: failed to execute command: command terminated with exit status=99\\n[stdout]\\nTue Jan 14 23:30:16 UTC 2020,k8s-agentpool1-37293710-0\\n\\n[stderr]\\n\\\"\\r\\n\\r\\nMore information on troubleshooting is available at https://aka.ms/VMExtensionCSELinuxTroubleshoot \"\r\n      }\r\n    ]\r\n  }\r\n}"}]
+ EXIT_VALUE=1
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
[Barnacle] 2020/01/14 23:43:15 Cleaning up Docker data root...
[Barnacle] 2020/01/14 23:43:15 Removing all containers.
... skipping 23 lines ...