[BUG] Private mediator fixture lacks its requested executable path #87

Closed
opened 2026-09-24 19:05:46 +02:00 by erikinkinen · 0 comments
Owner

Summary

The new actual mediator startup fixture requests bin/posixd through Exsh's existing cwd route, but the dynamic installer and loader graph currently expose only the executable-store spelling. This source-confirmed mismatch would prevent the first guarded preparation from reaching actual Posixd startup. It was found before the first VM attempt; no observed guest failure is claimed.

Reproduction

At Integration 9c5f766369d3ee9e3fdc8e59f16571dd4837f997, select tests/scenarios/appliance-disk-image-realm-startup-positive.toml. Exsh 2239d5faabc0a52091af921484bee6bb2d558c0b prepares the literal bin/posixd. Inspect install-dynlink-object-store.py, executable_alias_catalog.py and dynlink_runtime_graph.py: Posixd receives a store entry, while filesystem command aliases cover only Coreutils/Extop and the runtime graph uses the store source path. Loaderd requires an exact source-path graph match.

Expected and actual behavior

Explicitly packaging the startup mediator must expose /bin/posixd as a link to the same validated executable inode and bind that exact spelling to the matching runtime graph artifact. Images without Posixd must gain neither alias. The current source omits both aliases. Adding only a filesystem link would leave loader graph admission unsatisfied. The correction must add no ordinary launch sidecar, boot-service entry, client authority or extra cwd access.

Environment and identity

  • Component: signed Integration 9c5f766369d3ee9e3fdc8e59f16571dd4837f997, coherent 74-component image graph.
  • Image: opt-in actual mediator startup scenario, release binaries with the development runtime configuration.
  • Target: x86-64 EriX; first actual VM execution has not started.
  • Authority: existing scoped cwd SEND and authenticated Launchd route; the intended path stays unchanged.
  • Last known working revision: this is a newly introduced fixture; no previous actual Posixd guest acceptance exists.

Evidence and prior checks

The shared graph, strict component validation, dynamic Posixd artifact/dependency checks and helper suite passed, but those checks did not join the fixture's requested path to both filesystem and runtime-graph publication. A targeted regression will exercise that correspondence, same-inode link count, and the absence case before the first native attempt. Existing 120-second guest deadline, all earlier markers and ordinary shell exit remain mandatory.

Tracking

Older original CI follow-up — 25 September 2026: runs1784–1786 repeat realm PREPARE NOT_FOUND on their older source graphs; run1784 passes489/491, run1785 passes489/491 and run1786 passes490/491. The remaining failures in1784/1785 are separately tracked filesystem deadlines. These original graphs precede the accepted66ddc78/3d39c74 native startup witness. The historical observations do not retract that later scoped correction or claim complete client acceptance.

Historical CI and later native correction — 25 September 2026: original run1783 at 9c5f766369d3ee9e3fdc8e59f16571dd4837f997 passes490/491 scenarios; the sole failure is the realm startup scenario, whose first mediator PREPARE returns NOT_FOUND before the45-second progress watchdog. Its exact source predates both the alias correction ffedb3630895b2bc547ab58e4900f750d84cd64b and the private Launchd sidecar correction. This is historical evidence; the first internal refusal was not traced and no shared cause with the later START/INTERNAL defect is asserted.

The later signed Integration 66ddc78da31dd03dd554d0677cdc2af86588d525 / Launchd 3d39c7413a9c35a051323fceb7f895f0b18402e0 graph passes the maintained actual two-mediator startup witness with the original path,120-second hard and45-second progress limits. Both native Posixd instances become PrivateReady, retire independently and reject stale handles; ordinary shell exit completes. Exact image SHA-256 is ab4ef05766b71930d43fae69b445b4099265489fd0dc016483c3977d2b31ae8e;107 retained artifacts and55,891 serial bytes are reviewed, with zero build warnings, empty QEMU stderr and no cleanup failure. This satisfies the issue's corrected image/path gate and closes the alias defect. The four-client configuration/seal/I/O witness and full guest builds remain open.

Its first real Posixd PREPARE receives a valid typed NOT_FOUND rejection.

The original image, 107 evidence files and 56,013 serial bytes are retained. Rootd exits after the failed shell probe; the unchanged 45-second progress watchdog stops QEMU within its 120-second outer deadline. Exit E5 alone cannot identify Launchd: Exsh uses the same status, and the observed endpoint corresponds to the ordinary child range. Launchd issue 3 separately tracks a verified realm-event decoder gap; it is not established as the cause of this attempt. No unchanged failed input was rerun. Posixd startup, configuration/seal, client I/O and guest builds remain unaccepted; checklist progress stays 15.16%.

Older original Integration run 1779 passes all 490 catalog VMs and the unit suites, then fails a serial native-directory consent step. The distinct observation is recorded in existing regression 77, while regression 85 retains its earlier powerbox-input failure. Their root causes remain unresolved.

The filesystem link shares its validated executable inode, and the exact loader-graph source must match package identity and both manifest/content digests before filesystem effects. The ordinary launch-manifest generator emits no Posixd sidecar or authority row.

Six focused controls exercise the actual ext4 inode, link count, mode, bytes, installed graph, absent mediator and malformed evidence. Seven launch-flag tests and six existing packaging helpers pass; all complete validation logs have zero warnings. Both original regressions remain retained. The existing graph decoder is shared without changing its decoding behavior, and the maintained CI helper suite now contains 173 commands. All Rust and catalog inputs retain their prior validated bytes. This resolves the source mismatch in packaging regression 87; that issue stays open until the image and native path are exercised.

The first coherent actual startup VM is being prepared with the same requested path, existing scoped cwd and Launchd authority, earlier markers, ordinary shell exit and 120-second guest deadline. No actual Posixd guest execution, configuration/seal, client byte I/O or full guest build is accepted yet. Original Rootd CI 1043/1044 now passes, with all four complete logs and zero warnings/failures. New Integration CI is monitored separately; weighted checklist progress remains 15.16%, with 16/460 whole items accepted.

Related: startup implementation, WIP PR 12, and Phase 6 completion. Retain the original missing-alias regression and validate the corrected image before closing runtime acceptance.

Related records and contracts
Repository Links
launchd issue 4
## Summary The new actual mediator startup fixture requests `bin/posixd` through Exsh's existing cwd route, but the dynamic installer and loader graph currently expose only the executable-store spelling. This source-confirmed mismatch would prevent the first guarded preparation from reaching actual Posixd startup. It was found before the first VM attempt; no observed guest failure is claimed. ## Reproduction At Integration `9c5f766369d3ee9e3fdc8e59f16571dd4837f997`, select `tests/scenarios/appliance-disk-image-realm-startup-positive.toml`. Exsh `2239d5faabc0a52091af921484bee6bb2d558c0b` prepares the literal `bin/posixd`. Inspect `install-dynlink-object-store.py`, `executable_alias_catalog.py` and `dynlink_runtime_graph.py`: Posixd receives a store entry, while filesystem command aliases cover only Coreutils/Extop and the runtime graph uses the store source path. Loaderd requires an exact source-path graph match. ## Expected and actual behavior Explicitly packaging the startup mediator must expose `/bin/posixd` as a link to the same validated executable inode and bind that exact spelling to the matching runtime graph artifact. Images without Posixd must gain neither alias. The current source omits both aliases. Adding only a filesystem link would leave loader graph admission unsatisfied. The correction must add no ordinary launch sidecar, boot-service entry, client authority or extra cwd access. ## Environment and identity - Component: signed Integration `9c5f766369d3ee9e3fdc8e59f16571dd4837f997`, coherent 74-component image graph. - Image: opt-in actual mediator startup scenario, release binaries with the development runtime configuration. - Target: x86-64 EriX; first actual VM execution has not started. - Authority: existing scoped cwd SEND and authenticated Launchd route; the intended path stays unchanged. - Last known working revision: this is a newly introduced fixture; no previous actual Posixd guest acceptance exists. ## Evidence and prior checks The shared graph, strict component validation, dynamic Posixd artifact/dependency checks and helper suite passed, but those checks did not join the fixture's requested path to both filesystem and runtime-graph publication. A targeted regression will exercise that correspondence, same-inode link count, and the absence case before the first native attempt. Existing 120-second guest deadline, all earlier markers and ordinary shell exit remain mandatory. ## Tracking Older original CI follow-up — 25 September 2026: runs1784–1786 repeat realm PREPARE NOT_FOUND on their older source graphs; run1784 passes489/491, run1785 passes489/491 and run1786 passes490/491. The remaining failures in1784/1785 are separately tracked filesystem deadlines. These original graphs precede the accepted66ddc78/3d39c74 native startup witness. The historical observations do not retract that later scoped correction or claim complete client acceptance. Historical CI and later native correction — 25 September 2026: [original run1783](https://git.erikinkinen.fi/erix/integration/actions/runs/1783) at `9c5f766369d3ee9e3fdc8e59f16571dd4837f997` passes490/491 scenarios; the sole failure is the realm startup scenario, whose first mediator PREPARE returns NOT_FOUND before the45-second progress watchdog. Its exact source predates both the alias correction `ffedb3630895b2bc547ab58e4900f750d84cd64b` and the private Launchd sidecar correction. This is historical evidence; the first internal refusal was not traced and no shared cause with the later START/INTERNAL defect is asserted. The later signed Integration `66ddc78da31dd03dd554d0677cdc2af86588d525` / Launchd `3d39c7413a9c35a051323fceb7f895f0b18402e0` graph passes the maintained actual two-mediator startup witness with the original path,120-second hard and45-second progress limits. Both native Posixd instances become PrivateReady, retire independently and reject stale handles; ordinary shell exit completes. Exact image SHA-256 is `ab4ef05766b71930d43fae69b445b4099265489fd0dc016483c3977d2b31ae8e`;107 retained artifacts and55,891 serial bytes are reviewed, with zero build warnings, empty QEMU stderr and no cleanup failure. This satisfies the issue's corrected image/path gate and closes the alias defect. The four-client configuration/seal/I/O witness and full guest builds remain open. Its first real Posixd PREPARE receives a valid typed NOT_FOUND rejection. The original image, 107 evidence files and 56,013 serial bytes are retained. Rootd exits after the failed shell probe; the unchanged 45-second progress watchdog stops QEMU within its 120-second outer deadline. Exit E5 alone cannot identify Launchd: Exsh uses the same status, and the observed endpoint corresponds to the ordinary child range. [Launchd issue 3](https://git.erikinkinen.fi/erix/launchd/issues/3) separately tracks a verified realm-event decoder gap; it is not established as the cause of this attempt. No unchanged failed input was rerun. Posixd startup, configuration/seal, client I/O and guest builds remain unaccepted; checklist progress stays 15.16%. Older original Integration run 1779 passes all 490 catalog VMs and the unit suites, then fails a serial native-directory consent step. The distinct observation is recorded in [existing regression 77](https://git.erikinkinen.fi/erix/integration/issues/77), while [regression 85](https://git.erikinkinen.fi/erix/integration/issues/85) retains its earlier powerbox-input failure. Their root causes remain unresolved. The filesystem link shares its validated executable inode, and the exact loader-graph source must match package identity and both manifest/content digests before filesystem effects. The ordinary launch-manifest generator emits no Posixd sidecar or authority row. Six focused controls exercise the actual ext4 inode, link count, mode, bytes, installed graph, absent mediator and malformed evidence. Seven launch-flag tests and six existing packaging helpers pass; all complete validation logs have zero warnings. Both original regressions remain retained. The existing graph decoder is shared without changing its decoding behavior, and the maintained CI helper suite now contains 173 commands. All Rust and catalog inputs retain their prior validated bytes. This resolves the source mismatch in [packaging regression 87](https://git.erikinkinen.fi/erix/integration/issues/87); that issue stays open until the image and native path are exercised. The first coherent actual startup VM is being prepared with the same requested path, existing scoped cwd and Launchd authority, earlier markers, ordinary shell exit and 120-second guest deadline. No actual Posixd guest execution, configuration/seal, client byte I/O or full guest build is accepted yet. Original Rootd CI 1043/1044 now passes, with all four complete logs and zero warnings/failures. New Integration CI is monitored separately; weighted checklist progress remains 15.16%, with 16/460 whole items accepted. Related: [startup implementation](https://git.erikinkinen.fi/erix/integration/issues/1), [WIP PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12), and [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). Retain the original missing-alias regression and validate the corrected image before closing runtime acceptance. <details> <summary>Related records and contracts</summary> | Repository | Links | | --- | --- | | launchd | [issue 4](https://git.erikinkinen.fi/erix/launchd/issues/4) | </details>
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39:19 +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#87
No description provided.