Unable to deploy Azure Function App - error with storage account

0
votes

Lately I've had trouble with deploying a Function App via Azure CLI. Last week on Tuesday, I was still able to deploy a Function App via Azure CLI.

This week, like any other day before that, I used fairly common Azure Function Tools command func azure functionapp publish. The version of Azure Function Tools I am using is 3.0.3233.

Now I am getting this error every time:

Retry: 1 of 3
Error creating a Blob container reference. Please make sure your connection string in "AzureWebJobsStorage" is valid
Retry: 2 of 3
Error creating a Blob container reference. Please make sure your connection string in "AzureWebJobsStorage" is valid
Retry: 3 of 3
Error creating a Blob container reference. Please make sure your connection string in "AzureWebJobsStorage" is valid

I checked that AzureWebJobsStorage setting has a correct value, I even connected to storage account connection string via Azure Storage Explorer app.

Just in case, I created a new Function App in another region and I still get the same error.

Has anyone else encountered this error? I suspect this is an error in the tool itself, maybe a faulty build?

2
azureazure-functionsazure-cli
It's not a faulty build, I just checked that this happens also with version 2.7.3188 – devopsfanatic
Which trigger are you using? – akb
I could run func publish successfully a few hours ago on multiple hosting plans in East US. Build is 3.0.3233 too. Just to make sure, can you run func azure functionapp publish --debug ... and see if there's any useful information to help troubleshoot? – Max Ivanov
I use HTTP trigger. Even if I publish a brand new function app I get the same error. – devopsfanatic
I forgot to add: --debug flag does not reveal anything – devopsfanatic

2 Answers

0
votes

I suspect that AzureWebJobsStorage is not present/invalid in App Settings section of the function app in the Azure portal.

Make sure that it is added there and you are not deleting those settings through CLI/templates and recreating them without AzureWebJobsStorage.

0
votes

I answer to my own question. It seems that this was a transient error. Without changing any code, today I was able to redeploy my function app. Cheers.