Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

[stable/prometheus] Installation fails with: Release "metrics" failed: context canceled #17545

Closed
svparijs opened this issue Sep 30, 2019 · 3 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@svparijs
Copy link

svparijs commented Sep 30, 2019

Describe the bug
A clear and concise description of what the bug is.

Version of Helm and Kubernetes:
Kubernetes 1.13.10
Helm v2.14.3

Which chart:
Prometheus-operator 6.11.0

What happened:
While installing a clean prometheus-operator stack the response returns a: Release "metrics" failed: context canceled.

helm upgrade --install metrics stable/prometheus-operator -f values.yaml --namespace monitoring --debug
[debug] Created tunnel using local port: '49691'

[debug] SERVER: "127.0.0.1:49691"

[debug] Fetched stable/prometheus-operator to /Users/spa11916/.helm/cache/archive/prometheus-operator-6.11.0.tgz

Release "metrics" does not exist. Installing it now.
[debug] CHART PATH: /Users/spa11916/.helm/cache/archive/prometheus-operator-6.11.0.tgz

Error: release metrics failed: rpc error: code = Canceled desc = grpc: the client connection is closing

When looking at the configuration parts of the stack work.
Grafana is working as expected.
Alertmanager is working as expected.
Prometheus shows a few errors:
Screenshot 2019-09-30 at 15 06 03

Which shows the broken state.
metrics 1 Fri Sep 27 16:54:20 2019 FAILED prometheus-operator-6.11.0 0.32.0 monitoring

What you expected to happen:
A completely working prometheus-operator stack, as it previously did.

How to reproduce it (as minimally and precisely as possible):

helm secrets upgrade metrics --install stable/prometheus-operator -f values.yaml -f secrets.yaml --namespace monitoring

Anything else we need to know:

It previously worked. Currently it fails on Kubernetes version 1.12.8 as wel.

@svparijs
Copy link
Author

svparijs commented Oct 1, 2019

Its seems to be related to this: #6130 and #15977

The suggestion of helm/helm#6130 (comment) helped.
Incombination with clearing your helm cache.

@stale
Copy link

stale bot commented Oct 31, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 31, 2019
@stale
Copy link

stale bot commented Nov 14, 2019

This issue is being automatically closed due to inactivity.

@stale stale bot closed this as completed Nov 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

1 participant