Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Java 17 failing with "Could not find satisfied version for SemVer '17'" #692

Closed
edenman opened this issue Oct 10, 2024 · 14 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@edenman
Copy link

edenman commented Oct 10, 2024

Description:
This was working fine until today.

Task version:
v4

Platform:

  • Ubuntu
Current runner version: '2.320.0'
Runner name: 'android-16-core_d8ba276e3d05'
Runner group name: 'Android-CI'
Machine name: 'runner'
Operating System
  Ubuntu
  22.04.5
  LTS
Runner Image
  Image: ubuntu-22.04
  Version: 20241006.1.0
  Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20241006.1/images/ubuntu/Ubuntu2204-Readme.md
  Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20241006.1

Runner type:

  • Hosted

Repro steps:
Our config

            -   name: Set up JDK 17
                uses: actions/setup-java@v4
                with:
                    distribution: 'adopt'
                    java-version: 17

Expected behavior:
Install

Actual behavior:
Not installed

Run actions/setup-java@v4
  with:
    distribution: adopt
    java-version: 17
    java-package: jdk
    check-latest: false
    server-id: github
    server-username: GITHUB_ACTOR
    server-password: GITHUB_TOKEN
    overwrite-settings: true
    job-status: success
    token: ***
  env:
    PACKAGE_USERNAME: ***
    PACKAGE_TOKEN: ***
Installed distributions
  Trying to resolve the latest version from remote
  Error: Could not find satisfied version for SemVer '17'. 
@edenman edenman added bug Something isn't working needs triage labels Oct 10, 2024
@gplessis
Copy link

Looks like https://api.adoptopenjdk.net/ is currently in bad shape, throwing a 404.
https://www.eclipsestatus.io/ shows degraded services and an upcoming maintenance.

@edenman
Copy link
Author

edenman commented Oct 10, 2024

maybe adopt removed 17? switching to temurin seems to work if anybody else hits this

@genev
Copy link

genev commented Oct 10, 2024

We're seeing the same issue and the timing matches the downtime here: https://api.adoptopenjdk.net, like mentioned above.

@ahatzz11
Copy link

We've confirmed that zulu is also working after swapping to that over adopt:

    - name: Set up JDK 17
      id: setup-java
      uses: actions/setup-java@v4
      with:
        distribution: zulu
        java-version: 17

@maddyobrienjones
Copy link

running into this issue with jdk 11 on ubuntu as well

@muriloramos-hotmart
Copy link

muriloramos-hotmart commented Oct 10, 2024

Here i´m have problems with the 21 version.

I´m think to resolve need change the adopt values (https://github.com/search?q=repo%3Aactions%2Fsetup-java%20api.adoptopenjdk.net&type=code) to api.adoptium.net like in the page recommended https://api.adoptopenjdk.net/

@gowridurgad
Copy link

Hi @edenman,
Thank you for reporting this issue. We will investigate it and get back to you as soon as we have some feedback.

@marcinkubica
Copy link

'adopt' is now pulling from 'temurin' anyway

@violetagg
Copy link

Have this issue with GraalVM
Error: Could not find GraalVM for SemVer 17
on Ubuntu 20.04, MacOS 13, Windows 2022
https://github.com/reactor/reactor-netty/actions/runs/11370136940/job/31632048500

@johnoliver
Copy link

Have this issue with GraalVM Error: Could not find GraalVM for SemVer 17 on Ubuntu 20.04, MacOS 13, Windows 2022 https://github.com/reactor/reactor-netty/actions/runs/11370136940/job/31632048500

@violetagg from what I can tell, your issue is pulling graalvms that come from Oracle, the start of this issue was about pulling Adoptopenjdk/Temurin builds. I think yours is a separate issue

@violetagg
Copy link

@johnoliver Should I open a new issue? Btw we started to download the distribution manually in order to mitigate the problem.

@johnoliver
Copy link

@violetagg I would create a new issue yes, I think yours is unrelated to #692

@violetagg
Copy link

@johnoliver Here it is #700

@priyagupta108 priyagupta108 self-assigned this Oct 23, 2024
@priyagupta108
Copy link
Contributor

Hi @edenman 👋,
We've tested the issue on our end, and it appears to be resolved. Please try running your workflows again and let us know if the issue still persists.
Thanks!

@edenman edenman closed this as completed Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests