Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Barman 3.12.0 introduced a change that break the images #120

Closed
sxd opened this issue Nov 25, 2024 · 8 comments · Fixed by #119
Closed

Barman 3.12.0 introduced a change that break the images #120

sxd opened this issue Nov 25, 2024 · 8 comments · Fixed by #119
Assignees
Labels
bug Something isn't working

Comments

@sxd
Copy link
Member

sxd commented Nov 25, 2024

In the latest release of Barman 3.12.0 released on November 21th 2024, a change was introduced in this PR that changes the format of the date for the JSON output
to ISO format, which breaks the parsing of the backup being and end, this breaks the backups in the CloudNativePG operator.

The affected images are:

ghcr.io/cloudnative-pg/postgresql:12.22-3-bookworm@sha256:080144e45a6d70c8509383ce199e96d530a8005b75dc9b4eb7be91d36ae0b57f
ghcr.io/cloudnative-pg/postgresql:13.18-3-bookworm@sha256:85a27f658758bdf3ea1fe57d6d3508e9ac6fbf22bb55784f413ba92d87d200f9
ghcr.io/cloudnative-pg/postgresql:14.15-3-bookworm@sha256:42ebd0f2df0d79b607defd6df48f412cb3e30418227dc3dbb22d42c0fac339c4
ghcr.io/cloudnative-pg/postgresql:15.10-3-bookworm@sha256:dea6d0cd3e424ba972c9d6342558b966d6474d65e1ba73f303300709c755d805
ghcr.io/cloudnative-pg/postgresql:16.6-2-bookworm@sha256:0e3d584f1dbc9400c2a755e8b7739b7ece5cff2fb58140d3404f773422e15c45
ghcr.io/cloudnative-pg/postgresql:17.2-2-bookworm@sha256:a7ffdd12259075669df1d83cb4550171ff3f4a44cf5ec51a42a6ba8994503f84
ghcr.io/cloudnative-pg/postgresql:12.22-3-bullseye@sha256:bc24fe601f56d0b3b7b9d1e6579714e870202e4abc905d1fbbf895a30c0ca8f7
ghcr.io/cloudnative-pg/postgresql:13.18-3-bullseye@sha256:f176421039b990dc43bc1ee69229f01ac834658a104598ebee68e88fca1088dc
ghcr.io/cloudnative-pg/postgresql:14.15-2-bullseye@sha256:ee28b271ea01e860bbfdf6995e39a00c707014f0c6956bfd15836a37528d3d94
ghcr.io/cloudnative-pg/postgresql:15.10-2-bullseye@sha256:2b3da69b6c6e9989fa0150fee5709be5a55e10f14aff567188d2fb3f79981926
ghcr.io/cloudnative-pg/postgresql:16.6-2-bullseye@sha256:c368110f3fdfb5cadc0b15eb6f43f9899fb72db3d104bd68ecd9ed927dea0a06
ghcr.io/cloudnative-pg/postgresql:17.2-2-bullseye@sha256:bd9ffc16a3406cea7673df72c6a29d89fa395e00c01c91e1cc84bc67a6eb3440
ghcr.io/cloudnative-pg/postgresql:12.22-3-bullseye@sha256:bc24fe601f56d0b3b7b9d1e6579714e870202e4abc905d1fbbf895a30c0ca8f7
ghcr.io/cloudnative-pg/postgresql:13.18-3-bullseye@sha256:f176421039b990dc43bc1ee69229f01ac834658a104598ebee68e88fca1088dc
ghcr.io/cloudnative-pg/postgresql:14.15-2-bullseye@sha256:ee28b271ea01e860bbfdf6995e39a00c707014f0c6956bfd15836a37528d3d94
ghcr.io/cloudnative-pg/postgresql:15.10-2-bullseye@sha256:2b3da69b6c6e9989fa0150fee5709be5a55e10f14aff567188d2fb3f79981926
ghcr.io/cloudnative-pg/postgresql:16.6-2-bullseye@sha256:c368110f3fdfb5cadc0b15eb6f43f9899fb72db3d104bd68ecd9ed927dea0a06
ghcr.io/cloudnative-pg/postgresql:17.2-2-bullseye@sha256:bd9ffc16a3406cea7673df72c6a29d89fa395e00c01c91e1cc84bc67a6eb3440

Which are all the images built between November 22th to November 25th.
People that download the images should update the images to the latest one built after the following PR #119

@albundy83
Copy link

@sxd Hello, could you rebuild also image 16.5 please.
As the lastest one available 16.5-5 still contains barman 3.12 and causes the backup / timestamp issue described here

gbellongervais@localhost:~> podman run -it --entrypoint /bin/bash ghcr.io/cloudnative-pg/postgresql:16.5-5
postgres@fed603a8e170:/$ barman -v
3.12.0 Barman by EnterpriseDB (www.enterprisedb.com)

I have to rollback to 16.5-1 to find back barman 3.11:

gbellongervais@localhost:~> podman run -it --entrypoint /bin/bash ghcr.io/cloudnative-pg/postgresql:16.5-1
postgres@ca4cb2af2062:/$ barman -v
3.11.1 Barman by EnterpriseDB (www.enterprisedb.com)

Also, until a new fixed release is available, just 16.5 will send you to 16.5-5.
Thanks a lot for your help

@sxd
Copy link
Member Author

sxd commented Dec 1, 2024

@albundy83 you should try the latest 16.5-7 not the old ones, those were built before the update, we don't re-built old images, that will break immutability, you should just pull the latest one

@albundy83
Copy link

Hi, but there is no such image :)
That's why I asked you to prepare a new one please.
My aim was not to ask you to rebuild old images :)

@albundy83
Copy link

And when I try the last one, as I say in my first post, you have barman 3.12 (and the issue):

gbellongervais@localhost:~> podman run -it --entrypoint /bin/bash ghcr.io/cloudnative-pg/postgresql:16.5
postgres@d8e66b1fb8db:/$ barman -v
3.12.0 Barman by EnterpriseDB (www.enterprisedb.com)

@sxd
Copy link
Member Author

sxd commented Dec 1, 2024

@albundy83 sorry I mean 16.6, we don't built old 16.5 those are the buggy postgres images

@albundy83
Copy link

Ah ok, I understand, thanks for the details

@sxd
Copy link
Member Author

sxd commented Dec 1, 2024

@albundy83 please do not use 16.5 or any of PostgreSQL versions released on the week of Nov 14th

@albundy83
Copy link

Ok ok :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

Successfully merging a pull request may close this issue.

2 participants