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

helm errors are not logged to the console #29

Open
jandubois opened this issue Apr 1, 2023 · 1 comment
Open

helm errors are not logged to the console #29

jandubois opened this issue Apr 1, 2023 · 1 comment

Comments

@jandubois
Copy link

I had a broken repo, preventing helm upgrade from working:

$ helm "upgrade" "--install"  "--wait"  "ingress-nginx" "--create-namespace"  "--namespace"  "ingress-nginx" "https://github.com/kubernetes/ingress-nginx/releases/download/helm-chart-4.3.0/ingress-nginx-4.3.0.tgz"
Release "ingress-nginx" does not exist. Installing it now.
Error: no cached repo found. (try 'helm repo update'): open /Users/jan/Library/Caches/helm/repository/azure-index.yaml: no such file or directory

The output in the console however was just:

installing NGINX chart
Release "ingress-nginx" does not exist. Installing it now.
installed: you might need to restart docker-desktop if localhost:443 doesn't forward to nginx

Not sure if helm didn't return a non-zero exit code, but it seems that the STDERR output was getting lost.

@enrichman
Copy link
Member

Hi @jandubois, not sure about the reported issue. I have a different issue (a timeout) and I've seen that we are logging the stderr.

Do you know how to reproduce it?

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

2 participants