Azure-cli: Bad Request 400 with command 'az functionapp deployment source config-zip' for Linux function apps

[Bschitter]

Describe the bug
On running the command az functionapp deployment source config-zip -g myResourceGroup -n <app_name> --src <zip_file_path> the Azure CLI returns sometimes a Bad Request 400 error on Linux function apps.

To Reproduce

• az group create --name myResourceGroup --location westeurope
• az storage account create --name <storage_name> --location westeurope --resource-group myResourceGroup --sku Standard_LRS
• az functionapp create --resource-group myResourceGroup --consumption-plan-location westeurope --name <APP_NAME> --storage-account <STORAGE_NAME> --runtime <language> --os-type Linux
• az functionapp deployment source config-zip -g myResourceGroup -n <APP_NAME> --src <ZIP_FILE_PATH>

Only sometimes a Bad Request error happens and it seems to be only for Linux function apps. However the function will be correctly deployed and works afterwards.

Edit1:

ERROR: Operation failed with status: 'Bad Request'. Details: 400 Client Error: Bad Request for url: https://management.azure.com/subscriptions/XXX/resourceGroups/myResourceGroup/providers/Microsoft.Web/sites/<APP_NAME>/syncfunctiontriggers?api-version=2018-11-01

Expected behavior
Return no error, everything seems fine.

Environment summary
Azure CLI 2.0.73 from docker image mcr.microsoft.com/azure-cli:2.0.73

[msftbot[bot]]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @ ahmedelnably, @fabiocav

[rodbutters]

Getting same issue. Currently a blocker. Is there a work-around?

[ferantivero]

Also getting same issue here. @rodbutters In my case re-trying will do the trick

[slowtree]

Same here, looking at the logs it keeps saying missing authorization headers on trigger sync.
Operation failed with status: 'Bad Request'. Details: 400 Client Error: Bad Request for url: https://management.azure.com/subscriptions/ASUBSCR/resourceGroups/weathercachets/providers/Microsoft.Web/sites/ASITESS/syncfunctiontriggers?api-version=2018-11-01.

and then the link content is:
{"error":{"code":"AuthenticationFailed","message":"Authentication failed. The 'Authorization' header is missing."}}

It's really frustrating...

[thinkbeforecoding]

Same thing here.
And just a bit bore, the function that was working fine without any change started to return a 503 not available. The portal was displaying a 'The function runtime cannot be started'. I found nothing to make it work after that. I got randomly a 400 or 401 error while trying to upload the zip again.

[lobsteropteryx]

We are seeing the same thing--intermittent errors with zip deployments, and the occasional 503 from a deployed function app.

[hyperyn]

We're seeing this as well. It's only with Linux functions using Node runtimes.

[winseros]

Same here

[khmak3]

Same here. And this issue can be reproduce inside a linux docker easier

[igilham]

Here as well. My team had to do manual deployments because the tools could not be made to work.