Download Artifact task failing in getBuildApi with tunnel error
See original GitHub issueRequired Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: DownloadBuildArtifactsV0
Environment
-
Server - Azure Pipelines (YAML)
- If using Azure Pipelines, provide the account name, team project name, build definition name/build number: https://dev.azure.com/lloydslondon/Lloyds/_build/results?buildId=5669&view=results
-
Agent - Hosted
- If using Hosted agent, provide agent queue name: Lloyds-Hosted
Issue Description
When running a YAML pipeline, it always fails at the Download Artifact task from the deployment stage. Here is a link: https://dev.azure.com/lloydslondon/Lloyds/_build/results?buildId=5669&view=logs&j=22e8b1b6-9aa9-5014-5ac4-2849544435ca&t=d7adc642-3bc9-5b30-700a-e6d1dc3c194b&l=136
Task logs
Here are some truncated logs:
...
##[debug]Agent.ProxyUrl=http://proxy.***.net:8080 |
##[debug]Agent.ProxyUsername=DOMAINNAME\user_name |
##[debug]Agent.ProxyPassword=*** |
##[debug]Agent.ProxyBypassList=undefined
...
TUNNEL: making CONNECT request |
| Error: in getBuildApi, so retrying => retries pending : 4 |
| TUNNEL: tunneling socket could not be established, cause=socket hang up |
| Error: socket hang up |
| at createHangUpError (_http_client.js:253:15) |
| at Socket.socketOnEnd (_http_client.js:345:23) |
| at emitNone (events.js:91:20) |
| at Socket.emit (events.js:185:7) |
| at endReadableNT (_stream_readable.js:974:12) |
| at _combinedTickCallback (internal/process/next_tick.js:80:11) |
| at process._tickCallback (internal/process/next_tick.js:104:9)
...
##[error]Error: tunneling socket could not be established, cause=socket hang up
I prefer to send the full logs ZIP file via email and not post it here.
Troubleshooting
I have already identified the issue and I have the fix. It is related to the version of the tunnel
dependency. I will create a pull request shortly, but to the azure-devops-node-api repo, as that’s where the fix needs to go. I assume you will then change the version to your azure-devops-node-api
dependency in the DownloadBuildArtifactsV0
task.
Error logs
Error: tunneling socket could not be established, cause=socket hang up
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (6 by maintainers)
@omeshp can you please check if new tunnel version is resolving the issue. If yes, update task to take dependency on newer version of azure-devops-node-api.
This issue is stale because it has been open for a year with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days