Skip to content

Fixed hub install when PostgreSQL data or backup directory is a mount point (3.27.x) - #2583

Open
nickanderson wants to merge 1 commit into
cfengine:3.27.xfrom
nickanderson:ENT-14392/3.27.x
Open

nickanderson wants to merge 1 commit into
cfengine:3.27.xfrom
nickanderson:ENT-14392/3.27.x

Conversation

@nickanderson

@nickanderson nickanderson commented Oct 27, 2026 •

Copy link
Copy Markdown
Member

Backport of #2388

Ticket: ENT-14392

… point

`rm -rf` cannot remove a mount point even after emptying it, and the package
scripts treated that non-zero exit as failure. They now check whether the
directory ended up empty instead, run initdb via a staging directory when
nested mounts such as a separate pg_wal volume survive, and tolerate
lost+found in BACKUP_DIR.

Ticket: ENT-14392
Changelog: title
(cherry picked from commit 12aced1)
@nickanderson nickanderson changed the title Backported lost+found exemption to stale-backup guard (3.27.x) Fixed hub install when PostgreSQL data or backup directory is a mount point (3.27.x) Oct 27, 2026
@nickanderson

Copy link
Copy Markdown
Member Author

@cf-bottom jenkins, please

@cf-bottom

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants