fix: no first boot screen is drawn when nobody can answer the console #47
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/inithooks!47
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/dialog-unattended"
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?
keel#155, item 6: on a reboot, the first boot inithooks of a PostgreSQL container ran again.
Cause, reproduced on a new CT on BR1: a hook drew a screen on a console that nobody reads (
35pgsqlpassof common's pgsql overlay, with noDB_PASS). The first boot waited there for ever,98finalizedid not run andRUN_FIRSTBOOTstayedtrue. Each reboot ran every first boot hook again: new SSH host keys, and29sudoadminchanged the root password state.common#55 fixes that hook. This PR stops the same failure in any other hook:
runexportsINITHOOKS_UNATTENDED, and theDialogoflibinithooks/dialog_wrapper.pynow raises an error with that reason before it draws a widget. The hook fails,runlogs it and goes on, and the first boot ends. WithINITHOOKS_UNATTENDED=noor unset, nothing changes.Tests: written first,
TestNobodyCanAnswerintests/test_dialog_wrapper.py. Changelog: 2.3.6+keel26.