Hugo Bollon

So the last thing I see to try to debug this is to re-launch [multiple-minio-buckets](https://github.com/camptocamp/terraboard/tree/master/test/multiple-minio-buckets) test env, check the logs of Terraboard **and** Postgres to see if any errors occurs...

The endpoint `localhost:8080/api/lineages/states` doesn't exists However, `/api/lineages/stats` does. Can you try to make a request on it? FYI, a swagger documentation is served by default on the port 8081 where...

According to your logs, Terraboard finds two MinIO buckets but doesn't see any states in them. Do you have all required data under `./test/data/`? Does these directory aren't in read-only...

You definitely have an issue with MinIO containers. If you check your Terraboard's logs you will see that: `Found states from S3" bucket=test-bucket prefix= states=0` It should find some states...

So you have an issue with MinIO on your system: `WARNING: Host local has more than 0 drives of set. A host failure will result in data becoming unavailable`, however,...

We are currently running an instance on **Kubernetes** (and previously on **Openshift**) and I personally run the test environment without any troubles on **Ubuntu** and **Manjaro** (both amd64 Linux systems)...

@Jaff you can find our **Helm Chart** which is used to deploy our Terraboard instance on k8s [here](https://github.com/camptocamp/charts/tree/master/terraboard). @skasukur thanks for your catch, this file definitely needs an update, however,...

Hi @mmyrtekbmj ! Atm, Terraboard do not delete old state files which are deleted from fetching sources like S3. However, it's definitely a planned feature but without any ETA. If...

Hey @nishkrishnan ! Thanks for your issue, I plan to migrate from `aws-sdk-go` to `aws-sdk-go-v2` in the near future. I will replace `NewSession()` by `LoadDefaultConfig()`, it should resolve your case.

Hi @Weebimpaler The message `Reached end of service. Sleeping...` means that you're outside the operating hours configured for IGopher. There is the actual config that you have: ```yaml schedule: begin_at:...