Update PostgreSQL version used in Helm charts

[Martchus]

Maybe this helps with https://progress.opensuse.org/issues/188982.

[perlpunk]

If I understand bitnami/containers#83267 correctly, we can only use the latest version, not a specific version anymore.
But it seems to work, maybe because it is the latest version right now.

[Martchus]

But it seems to work, maybe because it is the latest version right now.

That was also a bit the idea behind this change and thus the version I put there is the latest¹. I don't know how to specify "latest" in these YAML files but that would probably be the best solution.

---

¹ Or at least the version mentioned on https://artifacthub.io/packages/helm/bitnami/postgresql?modal=install but that's probably the latest.

[perlpunk]

hm, it did not work after all :(
https://github.com/os-autoinst/openQA/actions/runs/18099813187/job/51499580830?pr=6786#step:7:211

Failed to pull image "docker.io/bitnami/postgresql:17.6.0-debian-12-r4": rpc error: code = NotFound

[perlpunk]

I don't know how to specify "latest" in these YAML files

Maybe just version: latest?

[Martchus]

No, but using '*' seems to work.

[Martchus]

This still doesn't work:

  Normal   Pulling    76s (x5 over 4m55s)   kubelet            Pulling image "docker.io/bitnami/postgresql:17.6.0-debian-12-r4"
  Warning  Failed     76s (x5 over 4m16s)   kubelet            Failed to pull image "docker.io/bitnami/postgresql:17.6.0-debian-12-r4": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/bitnami/postgresql:17.6.0-debian-12-r4": failed to resolve reference "docker.io/bitnami/postgresql:17.6.0-debian-12-r4": docker.io/bitnami/postgresql:17.6.0-debian-12-r4: not found
  Warning  Failed     76s (x5 over 4m16s)   kubelet            Error: ErrImagePull
  Warning  Failed     30s (x15 over 4m15s)  kubelet            Error: ImagePullBackOff
  Normal   BackOff    4s (x17 over 4m15s)   kubelet            Back-off pulling image "docker.io/bitnami/postgresql:17.6.0-debian-12-r4"

A local podman pull on the same image also leads to an error:

podman pull docker.io/bitnami/postgresql:17.6.0-debian-12-r4
Trying to pull docker.io/bitnami/postgresql:17.6.0-debian-12-r4...
Error: unable to copy from source docker://bitnami/postgresql:17.6.0-debian-12-r4: initializing source docker://bitnami/postgresql:17.6.0-debian-12-r4: reading manifest 17.6.0-debian-12-r4 in docker.io/bitnami/postgresql: manifest unknown

[perlpunk]

Maybe we can use https://hub.docker.com/r/bitnamilegacy/postgresql for now. I don't fully understand what they're doing, but that should give us a working check for now...

https://hub.docker.com/r/bitnami/postgresql is completely empty

[Martchus]

Looks like the container from bitnamisecure/postgresql is not a drop-in replacement. Not sure whether we should use bitnamilegacy/postgresql. We might as well remove the check completely if there's currently no sustainable Helm chart to satisfy the dependency on PostgreSQL. We might come up with our own container image and Helm char for PostgreSQL of course. I guess that would be out of scope for mitigating the failing checks, though.

[kalikiana]

Looks like the container from bitnamisecure/postgresql is not a drop-in replacement. Not sure whether we should use bitnamilegacy/postgresql.

Can you clarify what is missing? I can't seem to see the workflow, it just loads forever and remains empty

[Martchus]

Firefox also has problems showing the logs but it eventually shows:

>>> helm install openqa-g0cr8ajk8i charts/openqa --namespace openqa-g0cr8ajk8i --wait
Error: INSTALLATION FAILED: timed out waiting for the condition

and then many errors like this one further down below:

2025-09-29 16:13:47.887 GMT [4171] ERROR:  column d.daticulocale does not exist at character 289
2025-09-29 16:13:47.887 GMT [4171] HINT:  Perhaps you meant to reference the column "d.datlocale".
2025-09-29 16:13:47.887 GMT [4171] STATEMENT:  SELECT
	  d.datname as "Name",
	  pg_catalog.pg_get_userbyid(d.datdba) as "Owner",
	  pg_catalog.pg_encoding_to_char(d.encoding) as "Encoding",
	  CASE d.datlocprovider WHEN 'c' THEN 'libc' WHEN 'i' THEN 'icu' END AS "Locale Provider",
	  d.datcollate as "Collate",
	  d.datctype as "Ctype",
	  d.daticulocale as "ICU Locale",
	  d.daticurules as "ICU Rules",
	  pg_catalog.array_to_string(d.datacl, E'\n') AS "Access privileges"
	FROM pg_catalog.pg_database d
	ORDER BY 1;

[Martchus]

I changed it to use the legacy repo now. Let's see whether that works at least.

[Martchus]

I'm getting the same with the legacy repo now. I guess finding an exact constellation of Char and image that work together is taking too long now. So I'll create a PR disabling the check for now (so other PRs can at least be merged automatically again).

[Martchus]

One more attempt where I just change the container and not update the version of the Helm Chart.

[Martchus]

It still shows the same errors as in #6786 (comment). So I guess I can close this and we'll have to go with #6788 for now.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.25%. Comparing base (f221844) to head (09c72b6).
⚠️ Report is 25 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6786      +/-   ##
==========================================
- Coverage   99.25%   99.25%   -0.01%     
==========================================
  Files         402      402              
  Lines       41285    41285              
==========================================
- Hits        40979    40978       -1     
- Misses        306      307       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.