CI runner keel-lxc-1 fails every boot gate: containers start with no journal #61
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/tracker#61
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Since 2026-10-08 the boot-published-layer gate fails on keel-lxc-1 every time (3/3): mariadb.service fails at once and the container has no journal (journald down, the inithooks#38 symptom). The same test, layer and rootfs pass on every keel-lxc-2-* runner. keel-lxc-1 was green on 09-29/09-30, so the host changed (it is the production public services VM; the move to the dedicated runner VM is pending). Evidence: keel-mariadb evidence/2026-10-08-boot-gate.md. Action taken: keel-lxc-1 removed from the org runner pool so the gate runs only on keel-lxc-2-1..8; re-register it after the move.