This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 38%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDB%3C/text%3E%3C/svg%3E)
I have been developing a ML model using Azure ML workspace and the azure-ml SDK. The development of the model and deployment of the model works using the SDK. I have confirmed multiple times that after the endpoint is created I can call it with the correct payload and the webservice will return the correct results.
However, once I deploy a model to ACI and stop-start or restart the container instance resource in Azure. The endpoint stops working and I get a timeout error when calling the webservice.
Have any of you run into the same issues when deploying an Azure ML model to ACI?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 56.00000000000001%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIR%3C/text%3E%3C/svg%3E)
We are facing the same issue. Is there any tracker where I can track this issue?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 89%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
Any idea on this fix?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 1%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYM%3C/text%3E%3C/svg%3E)
@Luciano This has been fixed. Are you still seeing any issue regarding to it?
Regards,
Yutong
Yesterday we had an issue, and it looks as the same problem. We restarted the VM's associated to the AKS /AML and the Endpoint stop working. It's shows un-healthy. Today we started it again the VM and it works.
Thank you for the confirmation, this is a bug related to ACI and we have fixed it. Please let me know if you have more issue.
Regards,
Yutong
Hello,
The engineering team has confirmed this is a bug and we are in discussion about this bug. I will keep eyes on it and will let you know if there is any update. Thanks for reaching out to us.
Regards,
Yutong
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 46%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDB%3C/text%3E%3C/svg%3E)
Thank you! My team will be in anticipation of your research.
Hello everyone,
This issue has been confirmed fixed. It should work now with no issue. Please let me know if you are still suffering from bugs/ errors/...
Regards,
Yutong
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 0%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETJ%3C/text%3E%3C/svg%3E)
We have confirmed that the issue has been fixed. The endpoint can be called again after stopping and starting the ACI or after restarting the ACI.
We are having the same issue again right now
Hello, we are having the same issue today again. Are you sure that is correctly fixed?