Not Monitored
Tag not monitored by Microsoft.
39,298 questions
![](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(54.400000000000006, 23%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENA%3C/text%3E%3C/svg%3E)
run command prompt/ powershell/ VS code with administrator rights and then it will work
[Azure Bicep Deploy Issue] Error while attempting to retrieve the latest Bicep version: ('Connection aborted.'
Henry Zhang
206
Reputation points
Hello,
We are deploying to azure via Azure devops server release pipeline, the release was successful before. But when we tried again tonight, we got this error. We are running the Azure cli deploy command based on a bicep file.
az deployment group creat --template-file "XXXX.bicep" (other parameters as well, we got the right syntax)
Error we got:
ERROR: Error while attempting to retrieve the latest Bicep version: ('Connection aborted.', ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host', None, 10054, None)).
From the error message, looks like we can not download the newest version of Bicep.
Does anyone know why? Maybe an issue on Azure's side?
Btw, there is no tag for "Bicep" when I create this Q
Thanks
{count} votes
-
Henry Zhang 206 Reputation points
2023-05-12T04:06:39.9533333+00:00 update: we also tried to just run az bicep upgrade in a PowerShell script task step of the release pipeline. Got the same error. So looks like Azure-side issue. We are in Canada central
-
Dillon Silzer 57,491 Reputation points2023-05-12T04:15:14.8066667+00:00 Have you tried running this on a different network? Is your firewall perhaps blocking anything? Perhaps verify your connection string is correct.
-
Henry Zhang 206 Reputation points
2023-05-12T04:19:03.54+00:00 @Dillon Silzer Hi Dillon, in our PowerShell we also have other azure cli command,(like create resource group, check key-vault exist, query service principle info etc. ) they all run successfully. Only bicep-related commands failed. So I think it is not network related issue.
-
Henry Zhang 206 Reputation points
2023-05-12T04:21:04.5366667+00:00 @Dillon Silzer Hi Dillon, in our PowerShell, we also got other azure cli command like create resource group, query service principle id etc. They were all succeed, only the Bicep ones were failing. So I think it is not network related.
-
Dillon Silzer 57,491 Reputation points
2023-05-12T04:31:05.1733333+00:00 Were you trying to run the script a bunch of times tonight? Are you running it from the same IP address? Just from some research from some old github issues, there may be some rate limits per hour. Perhaps give it some time and try again.
-
Henry Zhang 206 Reputation points
2023-05-12T04:36:18.6266667+00:00 Only 1 script, since half of the script do succeed. I don't think it is rate limited
-
Henry Zhang 206 Reputation points
2023-05-12T04:43:45.3566667+00:00 Only 1 script, since half of the script were succeed but only bicep related command fails. I do not believe it were rate limted.
-
Henry Zhang 206 Reputation points
2023-05-12T15:24:57.43+00:00 OK, funny things happened. This morning another team member just tried to click the "deploy" button on the same release. Guess what, he succeeds! However, then I and another guy tried to click the same "deploy" button, and both of us failed and get this error again...
Sign in to comment