postgres-operator
postgres-operator copied to clipboard
[UI] No snapshots found in the backups tab
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

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

Has anyone made any progress on this issue except for the described workaround? This really cannot be a permanent fix, e.g. if the operator has to be recreated because of a node being drained, then the change in ui/operator_ui/spiloutils.py would be gone.