setup-java action failes on self-hosted runner with Error: aborted

[dzenansoftic]

Description:
When trying to download java 21 (distribution microsoft) the step failes after some retries, because it aborted without any error message or explanation. This is on a self-hosted runner. We have multiple workflows running at the same time on different self-hosted runners.

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Repro steps:
run the setup-java action in a self-hosted runner

Expected behavior:
Successful download

Actual behavior:
Action failes and only Error shown is aborted

[d3r3kk]

We cannot reproduce this issue from our network. Can you please provide further details by adding debug switches to the download task, or perhaps doing a traceroute from the agent prior to downloading (also, does your download agent deal with redirects well?)? Have you tried to do this manually from your own workstation using the same tool the agent does (ie. does the agent download tool deal with 302 redirects)? What happens if you try and download a different version (21.0.3 for instance)?

[aparnajyothi-y]

Hello @dzenansoftic, Thank you for creating this issue. The error message you encountered seems to be related to a server downtime.

We have run the same workflow on our end, and the setup job completed successfully. Please refer to the attached screenshots for your reference.

Could you please re-trigger the workflow on your end and confirm if the issue persists?

Feel free to reach out if you need any further clarifications.

[stefanschulte]

Just to provide some more context: I've seen the same error twice in the last 2 days, although my workflows run on github hosted default ubuntu runners.

Same error message. Download then again works fine when just re-running the same workflow again.

[aparnajyothi-y]

Hello @dzenansoftic, please let us know if the re-trigger resolved the issue. If you have any further concerns or questions, feel free to reach out.

[aparnajyothi-y]

Hello @dzenansoftic, gently following up to see if re-triggering the process has resolved the issue. If you have any further questions or concerns, please don’t hesitate to reach out.