Open SamirFarhat opened 5 years ago
The behavior is the same even when i provide a bad password of the CR server
Did the deployment eventually ever timeout?
I cancelled the deployment before its timed out, so i don't know if it will timeout. My problem is that it should fire an error as long as the image does not exist
Had a similar issue with a container that did not exist in the container repository. For me it timed out.
Deployment failed. Correlation ID: dfde86d3-1302-438e-ba48-2eaae9576101. {
"status": "Canceled",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Canceled'.",
"details": [
{
"code": "RequestTimeout",
"message": "The request timed out.",
"details": []
}
]
}
}
We need checks if registry access and container names are valid!
Hi, I noticed that when i deploy a SFM app, the deployment continues even when the image (Azure container registry) does not exist. I rather expected that an error message is thrown saying that the image does not exist.
Is this a bug ?