Function App Slot swap is failing with 'http ping' failure
See original GitHub issueI have several Azure pipelines that was using the below task to perform Slot swamp successfully, but these tasks are suddenly failing, this i noticed yesterday (7th Dec, 22). The swap was working till couple of days before that, i suspect there is some breaking change, or, a bug that is causing the issue. Please suggest solution.
steps:
- task: AzureAppServiceManage@0
displayName: 'Swap Slot'
inputs:
azureSubscription: ${{ parameters.serviceConnectionName }}
Action: 'Swap Slots'
WebAppName: '$(FunctionAppName)'
ResourceGroupName: '$(ResourceGroupName)'
SourceSlot: '$(SlotName)'
Error:
2022-12-07T12:45:26.1272981Z ##[warning]Error: Failed to update deployment history. Conflict (CODE: 409) 2022-12-07T12:45:26.1288473Z ##[error]Error: Failed to swap App Service ‘-func’ slots - ‘Staging’ and ‘production’. Error: ExpectationFailed - Cannot swap site slots for site '-func’ because the ‘Staging’ slot did not respond to http ping. (CODE: 417) 2022-12-07T12:45:26.1358404Z ##[section]Finishing: Swap Slot
Investigative information
Please provide the following:
- Timestamp: 2022-12-07T12:45:26.1272981Z
- Function App version: v3
- Deployment: https://****-func-staging.scm.azurewebsites.net/api/deployments/77431670417116365
- Region: northueurope
Thanks.
Issue Analytics
- State:
- Created 9 months ago
- Reactions:7
- Comments:35 (3 by maintainers)
Top Related StackOverflow Question
Folks, this issue has been identified and the team is actively deploying a patch to address the problem. We’ll provide updates here, but this should be addressed in a number of regions, so a retry is recommended.
With Azure DevOps Build Pipeline, we have the same issue since DockerInstaller@0.214.0. At the Build Pipeline, based on YAML, it is possible to Rollback to working DockerInstaller@0.209.0. But at the Azure DevOps Release Pipeline, based on the Visual Components, the DockerInstaller Task is fixed with Wildcard ‘0.*’ to the latest version, currently DockerInstaller@0.214.0. Our Workaround at the Azure DevOps Release Pipelines is “continue with error” under “Control Section” and an additional Bash Task that sets installed Docker CLI to the PATH Variable.
Bash Task with Inline Code for our Hosted Agent for Docker 20.10.22 (x64) ` export PATH=$PATH:/azp/_work/_tool/docker-stable/20.10.22/x64
chmod 777 /azp/_work/_tool/docker-stable/20.10.22/x64/docker `
Please create an Hotfix for DockerInstaller with an higher Version than 0.214.0, or add Version 0.209.0 to the “Task Version” Field at the Azure DevOps Release Task. Alternative change “Task Version” Field from SelectBox to Input Field so that the default value “0.*” can be overridden by the user.