-
Notifications
You must be signed in to change notification settings - Fork 76
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
Helm Kind action seems broken #42
Comments
interesting , I have been banging my head the past few hours with the exact same issue: https://github.com/sigstore/fulcio/pull/115/checks?check_run_id=2952287344#step:5:28 |
I'm going to try to reproduce the issue |
Just tried using container-tools/kind-action@v1 with the same result. So I assume it's most likely a GitHub Actions issue. |
manage to reproduce using the current action release: https://github.com/cpanato/testing-ci-providers/runs/2952724834?check_suite_focus=true however if I update the kind to be the latest one |
made a PR to update the kind for the action: #43 and asap we merge that I will make a new release |
yes, I would say as well, looks like some infrastructure change or have some issues in the gitHub side |
I can confirm, selecting v0.11.1 as kind version works. |
@ctron just made a new release of the action to defaults kind to v0.11.1 https://github.com/helm/kind-action/releases/tag/v1.2.0 will close this issue |
This is necessary to work around a probable GH infrastructure issue where 0.9.0 suddenly started not to work in GH Actions: helm/kind-action#42 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
This is necessary to work around a probable GH infrastructure issue where 0.9.0 suddenly started not to work in GH Actions: helm/kind-action#42 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
This is necessary to work around a probable GH infrastructure issue where 0.9.0 suddenly started not to work in GH Actions: helm/kind-action#42 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
This is necessary to work around a probable GH infrastructure issue where 0.9.0 suddenly started not to work in GH Actions: helm/kind-action#42 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
This is necessary to work around a probable GH infrastructure issue where 0.9.0 suddenly started not to work in GH Actions: helm/kind-action#42 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
This is necessary to work around a probable GH infrastructure issue where 0.9.0 suddenly started not to work in GH Actions: helm/kind-action#42 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
This is necessary to work around a probable GH infrastructure issue where 0.9.0 suddenly started not to work in GH Actions: helm/kind-action#42 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
This is necessary to work around a probable GH infrastructure issue where 0.9.0 suddenly started not to work in GH Actions: helm/kind-action#42 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
Signed-off-by: pmint93 <phamminhthanh69@gmail.com>
* iop: update revad and wopiserver versions to latest stable * ci: update the kind-action version to prevent timeouts - for reference: - helm/kind-action#42 - helm/kind-action#43
Thank you so much to those who worked on this! The cause for this doesn't seem clear from looking at this issue. Is this likely to happen again? Is there anything we can do in user-land to avoid it or at least make it explicit next time it happens? I would've never thought of checking this action, since it was being marked as successful -- the failure was just marked as a warning. |
To me it looks like the helm/kind-action is broken now in general. It fails to set up the network.
Also see: https://github.com/ctron/kind-reproducer/runs/2951832350?check_suite_focus=true
Note: The fact that job is finished completed seems to be another issue with this action: see #41
The text was updated successfully, but these errors were encountered: