[BUG] Missing-Procd fixture fails before the guest starts #129

Closed
opened 2026-10-15 05:47:53 +02:00 by erikinkinen · 2 comments
Owner

Summary

The missing-Procd negative fixture stops during image preparation instead of reaching its intended guest failure.

Reproduction

Run subsystem-missing-procd-negative on Integration 9c4b15c0. The fixture removes Procd before deployment capacities are derived, while keeping Loaderd. The unchanged production check refuses this input with production loader TLS requires packaged procd.

Expected and actual behavior

The fixture should prepare valid component capacities, then omit only Procd from the early-service handoff. Rootd should reject that handoff with the existing SERVICE_FAIL marker and exit 0x14. Instead, construction fails before a guest can start.

Environment and identity

Integration 9c4b15c0f0293c4a6d75b338b3ba99f5fcada763, release subsystem-negative fixture. The same preparation refusal appears in run 2645.

Evidence and prior checks

The selected module list omits Procd before capacity preparation. Rootd separately requires its actual early-service module before parsing the descriptive boot configuration. Keep the production TLS check, Loaderd and the original guest failure oracle intact.

Tracking

Phase completion · Implementation PR.

  • Prepare the complete component set without weakening production TLS checks.
  • Omit only Procd at the intended handoff in both packaging entry points.
  • Cover normal preparation, explicit omission and production refusal with host regressions.
  • Confirm the unchanged negative scenario reaches its guest failure.
## Summary The missing-Procd negative fixture stops during image preparation instead of reaching its intended guest failure. ## Reproduction Run `subsystem-missing-procd-negative` on Integration `9c4b15c0`. The fixture removes Procd before deployment capacities are derived, while keeping Loaderd. The unchanged production check refuses this input with `production loader TLS requires packaged procd`. ## Expected and actual behavior The fixture should prepare valid component capacities, then omit only Procd from the early-service handoff. Rootd should reject that handoff with the existing `SERVICE_FAIL` marker and exit `0x14`. Instead, construction fails before a guest can start. ## Environment and identity Integration `9c4b15c0f0293c4a6d75b338b3ba99f5fcada763`, release subsystem-negative fixture. The same preparation refusal appears in [run 2645](https://git.erikinkinen.fi/erix/integration/actions/runs/2645/jobs/1/attempt/1). ## Evidence and prior checks The selected module list omits Procd before capacity preparation. Rootd separately requires its actual early-service module before parsing the descriptive boot configuration. Keep the production TLS check, Loaderd and the original guest failure oracle intact. ## Tracking [Phase completion](https://git.erikinkinen.fi/erix/integration/issues/65) · [Implementation PR](https://git.erikinkinen.fi/erix/integration/pulls/12). - [x] Prepare the complete component set without weakening production TLS checks. - [x] Omit only Procd at the intended handoff in both packaging entry points. - [x] Cover normal preparation, explicit omission and production refusal with host regressions. - [x] Confirm the unchanged negative scenario reaches its guest failure.
Author
Owner

d6e8d94d keeps Procd available during capacity preparation and omits only its delivered early-service entry afterward. The production TLS refusal remains intact. Both packagers use the same explicit in-place selector, with full CR/LF and trailing-newline preservation. The unchanged guest scenario still needs to confirm the intended failure.

[d6e8d94d](https://git.erikinkinen.fi/erix/integration/commit/d6e8d94d638b86ea9f4d6253328b3774532c5062) keeps Procd available during capacity preparation and omits only its delivered early-service entry afterward. The production TLS refusal remains intact. Both packagers use the same explicit in-place selector, with full CR/LF and trailing-newline preservation. The unchanged guest scenario still needs to confirm the intended failure.
Author
Owner

The unchanged missing-Procd negative scenario now passes on Integration 63bb744d after the fixture repair in d6e8d94d. Full Procd, TLS and filesystem preparation completes; the fixture omits only the typed early Procd handoff. The original 0x14 guest-status check and both required markers pass, and ERIX_ROOTD:READY is absent.

The original case ran once and completed cleanup. All acceptance criteria for this fixture issue are now satisfied.

The unchanged missing-Procd negative scenario now passes on Integration `63bb744d` after the fixture repair in `d6e8d94d`. Full Procd, TLS and filesystem preparation completes; the fixture omits only the typed early Procd handoff. The original `0x14` guest-status check and both required markers pass, and `ERIX_ROOTD:READY` is absent. The original case ran once and completed cleanup. All acceptance criteria for this fixture issue are now satisfied.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:17 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#129
No description provided.