0
votes

We've configured and run Azure DevOps Pipeline builds and releases for a year plus. We deploy to Azure App Services. Recently we began migrating some app services into an ASE (Azure Service Environment). This has required creating new Release definitions to deploy to the new ASE instances of our sites. The new Release pipelines failed with various errors or warnings that all contained Error: getaddrinfo ENOTFOUND.

Examples:

Deployment Failed with Error: Error: Error: Failed to deploy web package to App Service. Error: getaddrinfo ENOTFOUND xxxx.scm.xxxx.appserviceenvironment.net xxxx.scm.xxxx.appserviceenvironment.net:443

 

2020-06-10T15:18:33.6525723Z ##[warning]Error: Failed to update deployment history. Error: getaddrinfo ENOTFOUND xxxx-staging.scm.xxxx.appserviceenvironment.net xxxx-staging.scm.xxxx.appserviceenvironment.net:443 2020-06-10T15:18:33.7227144Z ##[warning]Error: Failed to update deployment history. Error: getaddrinfo ENOTFOUND xxxx.scm.xxxx.appserviceenvironment.net xxxx.scm.xxxx.appserviceenvironment.net:443

getaddrinfo ENOTFOUND looks to be a generic error associated with a lot of different issues. Would like to know if anyone has encounteed and found a fix for it in the context of Azure DevOps releases into ASE.

1

1 Answers

4
votes

Answering my own question here. Maybe this will save someone the several hours of work it took me to find the solution.

The answer in our case was simple: Select the Default agent pool in the Releases Run on agent - Agent pool field. It appears this gets set to another value when creating a new release. Once Agent pool was set to Default, the error went away.

Releases task screenshot