I am having an issue with our production release pipeline and agent, specifically in that it is unable to download the artifact for release with IIS. On attempting to run the release, the Download Artifact step logs
2023-02-22T22:18:42.6467404Z ##[section]Starting: Download artifact - Build-Production-API-TypeScript - api
2023-02-22T22:18:42.7319251Z ==============================================================================
2023-02-22T22:18:42.7319957Z Task : Download build artifacts
2023-02-22T22:18:42.7320423Z Description : Download files that were saved as artifacts of a completed build
2023-02-22T22:18:42.7320695Z Version : 0.216.0
2023-02-22T22:18:42.7321076Z Author : Microsoft Corporation
2023-02-22T22:18:42.7321547Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/download-build-artifacts
2023-02-22T22:18:42.7321911Z ==============================================================================
2023-02-22T22:18:46.8249186Z C:\www\agents\release\externals\node10\bin\node.exe: --openssl-legacy-provider is not allowed in NODE_OPTIONS
2023-02-22T22:18:46.9425936Z ##[error]Exit code 9 returned from process: file name 'C:\www\agents\release\externals\node10\bin\node.exe', arguments '"C:\www\agents\release\_work\_tasks\DownloadBuildArtifacts_a433f589-fce1-4460-9ee6-44a624aeb1fb\0.216.0\main.js"'.
2023-02-22T22:18:46.9444047Z ##[section]Finishing: Download artifact - Build-Production-API-TypeScript - api
Why node is even involved is beyond me, but the same step in a different pipeline is just fine:
2023-02-22T21:58:17.1993657Z ##[section]Starting: Download artifact - Build-Dev-API-TypeScript - api
2023-02-22T21:58:17.3002355Z ==============================================================================
2023-02-22T21:58:17.3003614Z Task : Download build artifacts
2023-02-22T21:58:17.3006223Z Description : Download files that were saved as artifacts of a completed build
2023-02-22T21:58:17.3006760Z Version : 0.216.0
2023-02-22T21:58:17.3007603Z Author : Microsoft Corporation
2023-02-22T21:58:17.3008662Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/download-build-artifacts
2023-02-22T21:58:17.3009343Z ==============================================================================
2023-02-22T21:58:28.1109733Z Downloading artifacts for build: 1687
2023-02-22T21:58:28.4930789Z Downloading items from container resource #/6191210/api
2023-02-22T21:58:28.4931934Z Downloading artifact api from: https://dev.azure.com/IGTOperationServices//_apis/resources/Containers/6191210?itemPath=api&isShallow=true&api-version=4.1-preview.4
2023-02-22T21:58:29.2199004Z Downloading api/1687.zip to C:\www\agents\release\_work\r1\a\Build-Dev-API-TypeScript\api\1687.zip
2023-02-22T21:58:30.7748022Z Downloaded api/1687.zip to C:\www\agents\release\_work\r1\a\Build-Dev-API-TypeScript\api\1687.zip
2023-02-22T21:58:31.5079000Z Total Files: 1, Processed: 1, Skipped: 0, Failed: 0, Download time: 3.013 secs, Download size: 14.790MB
2023-02-22T21:58:31.5367659Z Successfully downloaded artifacts to C:\www\agents\release\_work\r1\a\Build-Dev-API-TypeScript\
2023-02-22T21:58:31.5410177Z ##[section]Finishing: Download artifact - Build-Dev-API-TypeScript - api
The easy answer is to turn off the NODE_OPTION that is complaining but it is required for our application. Both hosts have been validated to be running the same version of Windows, node, npm, and the agent, and I've even confirmed the only differences between the two release pipelines is IDs for things like variable and deployment groups. What am I missing?
