azure-cli: az functionapp Azure Cli deploy error (v2)

This is autogenerated. Please review and update as needed.

Describe the bug

Command Name az functionapp deployment source config-zip

Errors:

HTTPSConnectionPool(host='*************.azurewebsites.net', port=443): Read timed out. (read timeout=3)
Traceback (most recent call last):
python3.6/site-packages/urllib3/connectionpool.py, ln 387, in _make_request
    six.raise_from(e, None)
<string>, ln 2, in raise_from
python3.6/site-packages/urllib3/connectionpool.py, ln 383, in _make_request
    httplib_response = conn.getresponse()
lib/python3.6/http/client.py, ln 1331, in getresponse
    response.begin()
...
socket.timeout: The read operation timed out


python3.6/site-packages/requests/adapters.py, ln 529, in send
    raise ReadTimeout(e, request=request)
requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='*****************.scm.azurewebsites.net', port=443): Read timed out. (read timeout=3)

To Reproduce:

Deploy zipped publish package to Azure Function App service. using the following command

az functionapp deployment source config-zip -g [RESOURCE-GROUP ]-n [ FUNCTION APP NAME] --src publish.zip

Expected Behavior

Environment Summary

Linux-4.15.0-1082-azure-x86_64-with-debian-stretch-sid
Python 3.6.5
Installer: DEB

azure-cli 2.5.1 *

Additional Context

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 19
Comments: 34 (2 by maintainers)

Most upvoted comments

We’ve seen this as well, intermittently across many projects. Have opened an Azure support issue, but we never got this resolved.

lobsteropteryx on Jun 18, 2020

@RakeshMohanMSFT What is the resolution on this issue? Seems like people are still experiencing this issue.

clurdish on Aug 30, 2022

Not sure this is relevant today in 2022 - since there are native GitHub actions to do this, that works fantastically well. Here is an example:

# Deploy template
- name: Provision Azure Function App from Bicep
  id: functiondeploy
  uses: Azure/arm-deploy@v1
  env:
    DEPLOYMENT_NAME: FunctionDeploy-${{github.run_number}}
  with:
    resourceGroupName: ${{ inputs.targetResourceGroup }}

    template: ${{ inputs.buildOutputPath }}/bicep/main.bicep
    parameters: initiator=${{github.actor}}
    deploymentMode: Incremental
    deploymentName: ${{env.DEPLOYMENT_NAME}}


- name: Deploy Function App code
  uses: Azure/functions-action@v1
  with:
    app-name: ${{ steps.functiondeploy.outputs.functionName}}
    package: ${{ inputs.buildOutputPath }}/build

- name: Show Function deployment outputs
  run: |
   echo "function Name: ${{ steps.functiondeploy.outputs.functionName }}"
   echo "function Swagger URL: ${{ steps.functiondeploy.outputs.functionSwaggerURL }}"
   echo "function-URL=${{ steps.functiondeploy.outputs.functionSwaggerURL }}" >> $GITHUB_ENV

pinakighatak on Jun 27, 2022

I hit the same issue.

I added the --timeout 360 to my command and it seems to have made a difference.

Splaxi on Jan 13, 2021

Is there any progress on this issue? We have failing function deployments all over the place because of this.

arthfl on Aug 13, 2020

We get this problem as well, it can be quite intermittent

ttjackott on May 26, 2020

This issue is triggering in our project at least once every day, making our ADO pipeline fail.

Not sure this is relevant today in 2022 - since there are native GitHub actions to do this

@pinakighatak this issue isn’t about the github actions, and github actions can replace az cli only in some specific cases.

Closing this thread.

@RakeshMohanMSFT why? Please reopen

gukoff on Mar 30, 2023

Yes, we reuse the same slot for each deployment, then do a swap.

lobsteropteryx on Jan 21, 2021

I think I finally got to the bottom of this issue. It seems to be a resource problem, kudos to https://github.com/Azure/azure-cli/issues/11980#issuecomment-685823613.

I upgraded my service plan to a premium one and the problem seems to have gone away

sonic1981 on Sep 29, 2020

We found btw. out that (at least for our simple use-case), the app deployment works perfectly fine when you use az webapp instead of az functionapp. This makes this whole issue a bit weirder, but maybe this is helping somebody 😉

arthfl on Sep 17, 2020