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

railgun integration test: "helm repo add" not idempotent #80

Closed
mflendrich opened this issue Apr 12, 2021 · 1 comment · Fixed by #81
Closed

railgun integration test: "helm repo add" not idempotent #80

mflendrich opened this issue Apr 12, 2021 · 1 comment · Fixed by #81
Assignees
Labels
bug Something isn't working priority/low

Comments

@mflendrich
Copy link
Contributor

make -C ./railgun test.integration issues helm repo add kong which succeeds on the first run, but then fails on a subsequent run with an error that the kong repo already exists.

This does not surface on CI (because every run is in a clean environment) but gave me a spurious test error on my machine that took a while to debug.

@rainest
Copy link
Contributor

rainest commented Apr 19, 2021

There is a flag that should be able to work around this if it's not possible to ignore the error:

--force-update               replace (overwrite) the repo if it already exists

Not really its intended use, but 🤷

@shaneutt shaneutt self-assigned this Aug 4, 2021
@shaneutt shaneutt transferred this issue from Kong/kubernetes-ingress-controller Aug 4, 2021
@shaneutt shaneutt added the bug Something isn't working label Aug 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority/low
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants