Repository navigation
fix: deploy.sh and postgres/monitoring SSH-host install reliability - #108
Open
tkipkurgat wants to merge 1 commit into
Open
tkipkurgat wants to merge 1 commit into
tkipkurgat wants to merge 1 commit into
Conversation
- deploy.sh: added DEBIAN_FRONTEND=noninteractive and grub-pc
install_devices debconf pre-seeding for the controller's own apt
runs, via boot-disk auto-detection (lsblk/findmnt). Removed
--upgrade from the routine community.general collection install,
which was unintentionally upgrading collections on every run.
- postgres/tasks/ssh.yml and monitoring/tasks/ssh.yml: SSH-connected
hosts install packages over SSH too and were missing the same
grub-pc pre-seed. On QEMU/KVM VMs this debconf question can be
genuinely unanswered until a kernel-related update pulls grub-pc in
as a dependency, and DEBIAN_FRONTEND=noninteractive alone doesn't
help then - grub-install fails outright ("/multiselect does not
exist") instead of proceeding. Retries on the pre-seed itself since
a freshly-booted VM's own cloud-init/unattended-upgrades can still
be holding debconf's lock.
- postgresql-db.yml: trivial task-name capitalization fix
("creating..." -> "Creating...") for consistency with the rest of
the role.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
deploy.sh: addedDEBIAN_FRONTEND=noninteractiveand grub-pcinstall_devicesdebconf pre-seeding for the controller's own apt runs, via boot-disk auto-detection (lsblk/findmnt). Removed--upgradefrom the routinecommunity.generalcollection install, which was unintentionally upgrading collections (and their pinned module behavior) on every deploy run.postgres/tasks/ssh.ymlandmonitoring/tasks/ssh.yml: SSH-connected hosts install packages over SSH too and were missing the same grub-pc pre-seed already applied elsewhere. On QEMU/KVM VMs this debconf question can be genuinely unanswered until a kernel-related update pulls grub-pc in as a dependency -DEBIAN_FRONTEND=noninteractivealone doesn't help then, andgrub-installfails outright instead of proceeding. Retries on the pre-seed itself since a freshly-booted VM's own cloud-init/unattended-upgrades can still be holding debconf's lock.postgresql-db.yml: trivial task-name capitalization fix for consistency with the rest of the role.Test plan
deploy.shno longer upgrades installed Ansible collections on a routine run