ci: run smoke-full rootless, keep pod for diagnostics#31
Merged
Conversation
The first smoke-full run on main (27274677129) failed with 'systemd did not start in 30s' and the journal-dump step found nothing to inspect. Two causes: - The job ran podman as root (sudo). Root podman + systemd-in-container is broken on the ubuntu runners, and it was never the validated path — the end-to-end pass on 2026-06-09 was rootless. Drop sudo everywhere in the job (image build, smoke run, dump) so build and run share the same storage. - smoke-full.sh's cleanup trap removes the pod on exit, so the on-failure journal dump always saw 'no such container'. Set KEEP_POD=1 in the job (the runner is ephemeral) and dump the container console from the script itself before dying. Also raise the systemd boot wait from 30s to 60s for slower runners.
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.
The first smoke-full run on main (27274677129) failed with 'systemd did not start in 30s' and the journal-dump step found nothing to inspect.
Two causes:
Also raise the systemd boot wait from 30s to 60s for slower runners.