Skip to content

ci(startup): give the install container the host's udev database - #1129

Closed
Danathar wants to merge 1 commit into
mainfrom
ci/startup-install-udev
Closed

Danathar wants to merge 1 commit into
mainfrom
ci/startup-install-udev

Conversation

@Danathar

Copy link
Copy Markdown
Contributor

Summary: testsuite's VM checks can't install the current Dakota :testing image: bootc install stops with "root partition 3 has type " before it writes anything. This freezes v1 (#1123, held since 2026-11-09 09:41Z) and fails the startup checks on every PR that runs them (for example #1127). This PR tries the likely fix on the startup lane first. This PR's own startup checks are the test.

Why it fails

What changes

  • startup-qualification.yml: the install container also gets -v /run/udev:/run/udev.
  • docs/skills/ci-ops/e2e-workflow/references/troubleshooting.md: notes that the "race" explanation doesn't hold and that e2e.yml needs the same mount.

What happens next

  • If startup (candidate) gets past "Install OCI image to disk": the same one-line change goes into e2e.yml (a human-merge release workflow, so a separate PR), which un-freezes v1.
  • If it fails the same way: the cause is something else, and this PR should be closed.

e2e.yml isn't touched here.

Checks run locally

actionlint and zizmor report nothing new on startup-qualification.yml (main has the same 8 shellcheck notices and 1 zizmor finding). pytest and validate_docs.py run in CI.

Refs #1123

🤖 Generated with Claude Code

bootc 1.17 reads the new root partition's type with lsblk, which gets it
from the udev database. The startup lane's install container gets /dev
but not /run/udev, so on the current Dakota testing image bootc stops
with "root partition 3 has type <none>" before writing anything. The
startup checks have failed this way on every run since 2026-11-10, and
the v1 gate's boots fail the same way in e2e.yml (#1123). #1125's retries
don't help: all three attempts fail identically.

Mount /run/udev into the install container. This PR's own startup
checks are the test. If they pass, e2e.yml needs the same one-line mount
in a separate change, since it is a human-merge release workflow.

Refs #1123

Assisted-by: Claude Opus 5.5 via Claude Code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Danathar <Danathar@users.noreply.github.com>
@hivecommons-hive hivecommons-hive Bot added author/clanker A contributor's own hive authored this PR under their login dco All commits are DCO signed-off role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act and removed stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 10, 2026
@hivecommons-hive

Copy link
Copy Markdown
Contributor

@Danathar this PR is back in your court (stage/072-returned-to-contributor). The hive will not merge it until the head changes.

Failing checks:

  • startup (broken)

Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path.

Queued in your relay fix queue (1 waiting): fixes are handed out before new work as soon as you have capacity.

@hivecommons-hive

Copy link
Copy Markdown
Contributor
4984c62

ℹ️ Sentinel notice — informational; author is trusted (owner), merge is not blocked

Hive flagged this PR (author @Danathar, head 4984c628b1aa) because it matches behaviors that can override security controls, escalate privileges or damage the codebase. This is a heuristic, not an accusation — a maintainer should confirm the change is intended before it merges.

  • sensitive_path — changes 1 sensitive path(s) (Touches a sensitive path (OWNERS, workflows, policies, hive config, security docs, …))
    • .github/workflows/startup-qualification.yml

Hive did not add the sentinel-alert label because this author is trusted. The finding remains recorded for audit and the dashboard Security tab; set sentinel.trusted_authors_block: true to require the blocking label for trusted authors too.

@Danathar

Copy link
Copy Markdown
Contributor Author

The startup checks ran with the /run/udev mount and failed identically (run 42905999048), so this isn't the cause. Closing; details on #1123.

@Danathar Danathar closed this Nov 10, 2026
@Danathar
Danathar deleted the ci/startup-install-udev branch November 10, 2026 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author/clanker A contributor's own hive authored this PR under their login dco All commits are DCO signed-off role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/072-returned-to-contributor Contributor PR: CI red, changes requested or conflicting; diagnosis posted, author must act

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant