search

fluxcd / flux

Successor: https://github.com/fluxcd/flux2
https://fluxcd.io
Apache License 2.0
6.9k stars 1.08k forks source link

Unable to deploy promethues-operator helm chart #2623

Closed acarsercan closed 4 years ago

acarsercan commented 4 years ago

Hi, I'm unable to deploy helm chart promethues-operator using fluxcd.

Type     Reason       Age                 From                                                  Message
  ----     ------       ----                ----                                                  -------
  Normal   Scheduled    41m                 default-scheduler                                     Successfully assigned monitoring/promethues-operator-promet-operator-65499f749c-vds7p to ip-172-26-157-82.eu-west-2.compute.internal
  Warning  FailedMount  11m (x23 over 41m)  kubelet, ip-XXX.eu-west-2.compute.internal  MountVolume.SetUp failed for volume "tls-proxy-secret" : secrets "promethues-operator-promet-admission" not found
  Warning  FailedMount  75s (x18 over 39m)  kubelet, ip-XXX.eu-west-2.compute.internal  Unable to mount volumes for pod "promethues-operator-promet-operator-65499f749c-vds7p_monitoring(4cd48c75-0b9e-11ea-8a76-020f71fd47e4)": timeout expired waiting for volumes to attach or mount for pod "monitoring"/"promethues-operator-promet-operator-65499f749c-vds7p". list of unmounted volumes=[tls-proxy-secret]. list of unattached volumes=[tls-proxy-secret promethues-operator-promet-operator-token-dfd4m]

I can deploy the same chart successfully using helm install

To Reproduce Deploy helm chart promethues-operator using flux

Expected behavior Successful deployment of all objects

Logs

  ----     ------       ----                ----                                                  -------
  Normal   Scheduled    41m                 default-scheduler                                     Successfully assigned monitoring/promethues-operator-promet-operator-65499f749c-vds7p to ip-172-26-157-82.eu-west-2.compute.internal
  Warning  FailedMount  11m (x23 over 41m)  kubelet, ip-XXX.eu-west-2.compute.internal  MountVolume.SetUp failed for volume "tls-proxy-secret" : secrets "promethues-operator-promet-admission" not found
  Warning  FailedMount  75s (x18 over 39m)  kubelet, ip-XXX.eu-west-2.compute.internal  Unable to mount volumes for pod "promethues-operator-promet-operator-65499f749c-vds7p_monitoring(4cd48c75-0b9e-11ea-8a76-020f71fd47e4)": timeout expired waiting for volumes to attach or mount for pod "monitoring"/"promethues-operator-promet-operator-65499f749c-vds7p". list of unmounted volumes=[tls-proxy-secret]. list of unattached volumes=[tls-proxy-secret promethues-operator-promet-operator-token-dfd4m]

Additional context Add any other context about the problem here, e.g

Regards

hiddeco commented 4 years ago
  1. the name of your HelmRelease probably contains a typo, promethues-operator -> prometheus-operator
  2. the problem seems to be that the (by Helm) generated manifest refers to a non-existing secret (maybe because of the typo), I expect everything to work once this secret exists
acarsercan commented 4 years ago

Hi,

Thanks for the reply. Apologies for the typo, which I've corrected but didn't fix the issue. tls-proxy-secret is part of a Job to be created when the helm chart is installed, however it is failing

Similar error reported in ArgoCD https://github.com/coreos/prometheus-operator/issues/2770

acarsercan commented 4 years ago

false positive

  17   │       admissionWebhooks:
  18   │         enabled: true