fix: a preset disables postgresql-common's WAL archival (keel#201) #4
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/no-wal-archival-preset"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Run 2 of the LNPP 19.0-3 release test (keel 0.23.41):
keel diffon the witness saiddatabase.server.role: drift (declared standalone, observed primary).pg_receivewal@17-mainstreamed from the server since the first boot (keel#201).systemd applies the presets on the first boot of an image (no machine-id). Debian's presets enable every unit they do not name, and postgresql-common's
pg_receivewal@isWantedBy=postgresql@%i.service. So every LNPP node archived its WAL into/var/backups/postgresql, held the slotpg_receivewal_service, and read as a primary in keel diff; on a standby the unit restarted in a loop.overlay/usr/lib/systemd/system-preset/20-keel-lnpp.presetdisablespg_receivewal@.serviceandpg_compresswal@.timer, as keel-overlay-etcd does for etcd.conf.d/zz-checkfails the build when the preset does not disable them, or when a link enables them.Tests:
tests/image-check.bats(no preset fails the build; an enabled link fails the build). The boot proof is run 3 of the LNPP release test on the image built from this. Theappliancegate does not boot this layer (no lnpp layer on the mirror).5afa867361f357df0cda