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

Intermittent fail #22

Open
jan-sykora opened this issue Jan 18, 2023 · 4 comments
Open

Intermittent fail #22

jan-sykora opened this issue Jan 18, 2023 · 4 comments

Comments

@jan-sykora
Copy link

When running the setup-k3d-k3s in our Github workflow we sometimes get an error.

Setup:

jobs:
  some-job:
    steps:
      - name: Set up k3d
         uses: nolar/setup-k3d-k3s@v1
         with:
           version: v1.20

Error:

Run nolar/setup-k3d-k3s@v1
  with:
    version: v1.20
    k3d-tag: latest
  env:
    MSYS: winsymlinks:nativestrict
Run /home/runner/work/_actions/nolar/setup-k3d-k3s/v1/action.sh
  /home/runner/work/_actions/nolar/setup-k3d-k3s/v1/action.sh
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    MSYS: winsymlinks:nativestrict
    VERSION: v1.20
    K3D_TAG: latest
    K3D_NAME: 
    K3D_ARGS: 
    GITHUB_TOKEN: 
    SKIP_CREATION: 
    SKIP_READINESS: 
Error: Process completed with exit code 22.

Based on the exit code it seems that the curl command in action.sh got 401 Unauthorized. This error occurs irregularly (when running the same setup).

@sprutton1
Copy link

We see this issue fairly often. Is there any progress here?

@nolar
Copy link
Owner

nolar commented Jul 24, 2023

Sorry, there is no sufficient information to debug the issue. It does not happen to me. If you find the cause and make a fix, please send a PR.

What I can assume blindly, if GITHUB_TOKEN is not set, is that you hit the GitHub rate limit for unauthorized users.

@sprutton1
Copy link

Thanks, I'll try adding the token. If the issue comes up again I'll see if I can get more info and let you know what's happening.

@jan-sykora
Copy link
Author

Unfortunately, the only workaround that worked for us was to setup k3d/k3s manually (not using the setup-k3d-k3s action). We didn't change anything else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants