Azure / Azure/azure-cli-extensions
AKS Deployment Failing but ACI and Local Deployment are not
- Dominant language
- Python
- Stars
- 454
- Forks
- 1.7k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 64
Description
- If the issue is to do with Azure CLI 2.0 in-particular, create an issue here at [Azure/azure-cli](https://github.com/Azure/azure-cli/issues)
### Extension name (the extension in question)
azure-cli-ml
### Description of the issue (in as much detail as possible)
With the same `score.py` file local and ACI deployment works just fine but AKS deployment throws an error. The error message is below:
```
2020-05-14T15:24:54.7319755Z {'Azure-cli-ml Version': '1.5.0', 'Error': WebserviceException:
2020-05-14T15:24:54.7320539Z Message: Service deployment polling reached non-successful terminal state, current service state: Failed
2020-05-14T15:24:54.7321105Z Operation ID: 3a7e2240-f43d-41b6-86ac-65885509275f
2020-05-14T15:24:54.7321833Z More information can be found using '.get_logs()'
2020-05-14T15:24:54.7322053Z Error:
2020-05-14T15:24:54.7322197Z {
2020-05-14T15:24:54.7322374Z "code": "KubernetesDeploymentFailed",
2020-05-14T15:24:54.7322606Z "statusCode": 400,
2020-05-14T15:24:54.7322828Z "message": "Kubernetes Deployment failed",
2020-05-14T15:24:54.7323059Z "details": [
2020-05-14T15:24:54.7323207Z {
2020-05-14T15:24:54.7323399Z "code": "CrashLoopBackOff",
2020-05-14T15:24:54.7325304Z "message": "Your container application crashed. This may be caused by errors in your scoring file's init() function.\nPlease check the logs for your container instance: my-test-container-aks. From the AML SDK, you can run print(service.get_logs()) if you have service object to fetch the logs. \nYou can also try to run image mymlws7d807d63.azurecr.io/azureml/azureml_93d2d3ddf88806afec6ed19187e8f46a:latest locally. Please refer to http://aka.ms/debugimage#service-launch-fails for more information."
2020-05-14T15:24:54.7326507Z }
2020-05-14T15:24:54.7326775Z ]
2020-05-14T15:24:54.7326912Z }
2020-05-14T15:24:54.7327058Z InnerException None
2020-05-14T15:24:54.7327239Z ErrorResponse
2020-05-14T15:24:54.7327380Z {
2020-05-14T15:24:54.7327536Z "error": {
2020-05-14T15:24:54.7330427Z "message": "Service deployment polling reached non-successful terminal state, current service state: Failed\nOperation ID: 3a7e2240-f43d-41b6-86ac-65885509275f\nMore information can be found using '.get_logs()'\nError:\n{\n \"code\": \"KubernetesDeploymentFailed\",\n \"statusCode\": 400,\n \"message\": \"Kubernetes Deployment failed\",\n \"details\": [\n {\n \"code\": \"CrashLoopBackOff\",\n \"message\": \"Your container application crashed. This may be caused by errors in your scoring file's init() function.\\nPlease check the logs for your container instance: my-test-container-aks. From the AML SDK, you can run print(service.get_logs()) if you have service object to fetch the logs. \\nYou can also try to run image mymlws7d807d63.azurecr.io/azureml/azureml_93d2d3ddf88806afec6ed19187e8f46a:latest locally. Please refer to http://aka.ms/debugimage#service-launch-fails for more information.\"\n }\n ]\n}"
2020-05-14T15:24:54.7332819Z }
2020-05-14T15:24:54.7332959Z }}
```
Contributor guide
Assessment
This issue has not been assessed yet.