Charts: [bitnami/thanos] thanos: error: expected command but got "bucket"

[dbrennand]

Which chart:
bitnami/thanos:
Output from helm list:
thanos monitoring 1 2020-06-25 09:23:39.9358571 +0000 UTC deployed thanos-1.1.1 0.13.0

Describe the bug
When installing the chart, the bucketweb container fails to start and the following error is produced in the logs:

Error parsing commandline arguments: expected command but got "bucket"
thanos: error: expected command but got "bucket"

To Reproduce
Steps to reproduce the behavior:

1. Follow the steps provided here:
   

I am using the following values.yaml file:

objstoreConfig: |-
  type: AZURE
  config:
    storage_account: "thanosstor"
    storage_account_key: "redacted"
    container: "thanosdata"
    endpoint: "https://thanosstor.blob.example.endpoint.com/"
    max_retries: 0
querier:
  dnsDiscovery:
    sidecarsService: prometheus-operator-prometheus-thanos
    sidecarsNamespace: monitoring
bucketweb:
  enabled: true
compactor:
  enabled: true
storegateway:
  enabled: true
ruler:
  enabled: true
  alertmanagers:
    - http://prometheus-operator-alertmanager.monitoring.svc.cluster.local:9093
  config: |-
    groups:
      - name: "metamonitoring"
        rules:
          - alert: "PrometheusDown"
            expr: absent(up{prometheus="monitoring/prometheus-operator"})
metrics:
  enabled: true
  serviceMonitor:
    enabled: true

Expected behavior
The helm chart deploys successfully first time without the container failing.

Version of Helm and Kubernetes:

• Output of helm version:

version.BuildInfo{Version:"v3.2.4", GitCommit:"0ad800ef43d3b826f31a5ad8dfbb4fe05d143688", GitTreeState:"clean", GoVersion:"go1.13.12"}

• Output of kubectl version:

Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.2", GitCommit:"52c56ce7a8272c798dbc29846288d7cd9fbae032", GitTreeState:"clean", BuildDate:"2020-04-16T11:56:40Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.5", GitCommit:"bb95a3814e91321a3821d669afc3707a8f35015f", GitTreeState:"clean", BuildDate:"2020-04-28T22:50:11Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Additional context
Command provided via args shown in kubectl describe pod thanos-webbucket-* -n monitoring:

    Args:
      bucket
      web
      --http-address=0.0.0.0:8080
      --log.level=info
      --objstore.config-file=/conf/objstore.yml
      --refresh=30m
      --timeout=5m

[miguelaeh]

Hi @dbrennand .
thank you very much for reporting the issue, the command has changed, we will take care of it.

[dbrennand]

How long does it take before I can use this fix?

I have ran helm repo update and it's still using the broken version.

[miguelaeh]

Hi @dbrennand ,
Sorry for the time this release is taking. A new version of Thanos appeared that is failing in our internal pipeline and because of that it is not being released. The changes will be published once we fix the issues with this new version. In the meantime, you can use this new version by cloning this repository and executing from the root of the repo:

helm install bitnami/thanos

That will take the latest changes in the repo instead of the package from Helm registry

[dbrennand]

@miguelaeh
I cloned the repo and from the root of the repo ran:
helm install thanos bitnami/thanos --namespace monitoring --values=.\thanos-values.yaml
I recieved the following error:
Error: found in Chart.yaml, but missing in charts/ directory: minio
🤔

[miguelaeh]

That should be that you don't have the proper dependencies in the charts directory. Try to execute:

helm dependencies update

We are sorry for the time this is taking, we have an issue in our internal workflow that is affecting the Thanos releases.

[dbrennand]

Hi @miguelaeh
Has the issue internally been fixed yet?

[dani8art]

Hi @dbrennand we are actively working on fixing it but unfortunately it wasn't fixed yet. Was the workaround to install the chart useful for you?

[dbrennand]

Thanks for your reply @dani8art
The workaround did work. However, it isn't ideal 😄I will be awaiting the release 👍

[dbrennand]

Hey guys, Is commit 3c3f801 the new release? Did you guys sort it? 😄
@dani8art @miguelaeh

[joancafom]

Hi @dbrennand ,

Yes, I have been able to check that the latest release contains the changes associated to the PR! 🚀

Thanks for your issue and apologies on the delay.