[BUG] Existing pipeline file-descriptor VM reports a redirection failure #91

Open
opened 2026-09-25 04:31:04 +02:00 by erikinkinen · 1 comment
Owner

Summary

The pipeline descriptor-redirection VM fails while launching a later child.
In CI 2822, Launchd rejects BEGIN with RESOURCE_EXHAUSTED even though the pool
has enough free receipt slots in total.

Reproduction

Run the existing appliance-disk-image-initial-exsh-pipeline-fd-script-positive
scenario through scripts/run-scenario.sh with its selected component graph,
signing fixtures and media. Original CI 2822
at Integration f06bf72280eff2f49248ce816c327f8a3760a4f4 records the failure.

Expected and actual behavior

The descriptor script must emit ERIX_EXSH:PIPELINE_FD_OK., both shell exit
acknowledgments and the expected native exit within the existing limits.
Instead, BEGIN returns result 7 and the guest emits
ERIX_ROOTD:INITIAL_EXSH:PIPELINE_FAILED:FD_REDIRECTION.

Retaining the first child’s cleanup handle splits the free receipt pool. A later
child needs a contiguous range. Reserving from the highest available range keeps
those retained handles together and leaves space for the next child.

Environment and identity

  • Release appliance, development runtime, one x86-64 vCPU and VirtIO/GPT media.
  • Original QEMU ceiling 120 seconds and serial-progress deadline 45 seconds.
  • CI 2822: VM job 48883, task 35275, attempt 1; pipeline worker 4.
  • Earlier CI 1788 and later companion runs also recorded pipeline failures.
    Equality of their generated artifacts remains unproved; the current diagnosis
    does not establish one cause for every historical observation.

Evidence and prior checks

Launchd 6c9e265a
contains the highest-first reservation fix. Its complete CI 422 passes 695 Rust
controls and 23 Markdown files without Rust warnings, including six new controls
for pipeline children, capacity, live reservations and uncertain cleanup.
Host controls do not establish that the original VM now passes.

Tracking

Related: Integration PR #12,
Launchd PR #2 and
Phase 6 completion.

  • Repair receipt fragmentation while preserving capability checks and cleanup ownership.
  • Cover pipeline children, exhausted capacity and uncertain cleanup.
  • Pass the original pipeline VM with its existing markers, native exit and time limits.
## Summary The pipeline descriptor-redirection VM fails while launching a later child. In CI 2822, Launchd rejects BEGIN with RESOURCE_EXHAUSTED even though the pool has enough free receipt slots in total. ## Reproduction Run the existing `appliance-disk-image-initial-exsh-pipeline-fd-script-positive` scenario through `scripts/run-scenario.sh` with its selected component graph, signing fixtures and media. Original [CI 2822](https://git.erikinkinen.fi/erix/integration/actions/runs/2822) at Integration `f06bf72280eff2f49248ce816c327f8a3760a4f4` records the failure. ## Expected and actual behavior The descriptor script must emit `ERIX_EXSH:PIPELINE_FD_OK.`, both shell exit acknowledgments and the expected native exit within the existing limits. Instead, BEGIN returns result 7 and the guest emits `ERIX_ROOTD:INITIAL_EXSH:PIPELINE_FAILED:FD_REDIRECTION`. Retaining the first child’s cleanup handle splits the free receipt pool. A later child needs a contiguous range. Reserving from the highest available range keeps those retained handles together and leaves space for the next child. ## Environment and identity - Release appliance, development runtime, one x86-64 vCPU and VirtIO/GPT media. - Original QEMU ceiling 120 seconds and serial-progress deadline 45 seconds. - CI 2822: VM job 48883, task 35275, attempt 1; pipeline worker 4. - Earlier CI 1788 and later companion runs also recorded pipeline failures. Equality of their generated artifacts remains unproved; the current diagnosis does not establish one cause for every historical observation. ## Evidence and prior checks [Launchd 6c9e265a](https://git.erikinkinen.fi/erix/launchd/commit/6c9e265a9de2154100191f28ed1d93affcbd141a) contains the highest-first reservation fix. Its complete CI 422 passes 695 Rust controls and 23 Markdown files without Rust warnings, including six new controls for pipeline children, capacity, live reservations and uncertain cleanup. Host controls do not establish that the original VM now passes. ## Tracking Related: [Integration PR #12](https://git.erikinkinen.fi/erix/integration/pulls/12), [Launchd PR #2](https://git.erikinkinen.fi/erix/launchd/pulls/2) and [Phase 6 completion](https://git.erikinkinen.fi/erix/integration/issues/65). - [x] Repair receipt fragmentation while preserving capability checks and cleanup ownership. - [x] Cover pipeline children, exhausted capacity and uncertain cleanup. - [ ] Pass the original pipeline VM with its existing markers, native exit and time limits.
Author
Owner

The failed pipeline runs out of contiguous receipt slots after its first child commits. Keeping that child’s cleanup handle in the middle of the pool leaves enough free slots in total, but no range large enough for the next child.

Launchd 0039c4d1 reserves from the highest available range, so retained cleanup handles leave the lower range contiguous. Integration now selects this revision. New controls cover both pipeline directions, three children, exhausted capacity and uncertain cleanup. The full component checks and the existing pipeline VM are still pending; the issue remains open.

The failed pipeline runs out of contiguous receipt slots after its first child commits. Keeping that child’s cleanup handle in the middle of the pool leaves enough free slots in total, but no range large enough for the next child. [Launchd 0039c4d1](https://git.erikinkinen.fi/erix/launchd/commit/0039c4d1bc9e4edfba0388ec19c3f3f49b99c8e6) reserves from the highest available range, so retained cleanup handles leave the lower range contiguous. Integration now selects this revision. New controls cover both pipeline directions, three children, exhausted capacity and uncertain cleanup. The full component checks and the existing pipeline VM are still pending; the issue remains open.
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#91
No description provided.