zalando / zalando/postgres-operator

[UI] No snapshots found in the backups tab

Open
#1,365 1 comment 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
5.2k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
3

Description

Please, answer some short questions which should help us to understand your problem / question better?

  • Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.6.0
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? Bare Metal K8s
  • Are you running Postgres Operator in production? yes
  • Type of issue? Bug report/question

Hi all.
I've got a problem with fetching backup list from minio
On UI I see clusters and their ID's, but then I've got no snapshots found

Screenshot from 2021-02-15 14-18-43

Under

bucket-name/spilo/{cluster-name}/{cluster_id_hash}/wal/{pg_version}/

I've got 2 dirs

basebackups_005
wal_005

In logs I've only got
http://postgres-operator-ui/stored_clusters/{cluster_name}/{cluster_id_hash} 200 OK

If I curl the same URL, I've got empty json, but I've got some data in minio.

UI configs

            - name: "TARGET_NAMESPACE"
              value: "*"
            - name: "AWS_ENDPOINT"
              value: "http://minio-service:9000"
            - name: "AWS_ACCESS_KEY_ID"
              value: "access"
            - name: "AWS_SECRET_ACCESS_KEY"
              value: "secret"
            - name: "SPILO_S3_BACKUP_BUCKET"
              value: "bucket-name"
            - name: "SPILO_S3_BACKUP_PREFIX"
              value: "spilo/"
            - name: "WALE_S3_ENDPOINT"
              value: "http+path://minio-service:9000

Minio credentials are populated with operator pod-configmap

Update. After updating spiloutils.py file as mentioned in
https://github.com/zalando/postgres-operator/issues/937#issuecomment-752280357

It starts working, but I've got 2 entries on UI for each backup
Screenshot from 2021-02-15 14-36-24

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the stored_clusters/{cluster_name}/{cluster_id_hash} endpoint and the spiloutils.py change referenced in the issue. Reproduce the empty response against the configured MinIO bucket, then verify that the backups tab lists existing snapshots once rather than returning no snapshots or duplicates.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, postgresql, python
Domain
backend, databases, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.