[BUG] Scenario preparation hides disk generator failures #127

Closed
opened 2026-10-15 04:54:39 +02:00 by erikinkinen · 1 comment
Owner

Summary

Scenario preparation can continue after its block-image generator fails. It
reports the intended image path and starts fixture work before a later missing
disk error replaces the original failure.

Reproduction

Run 2645,
subsystem-ext4-acl-metadata-positive, raised an ACL fixture
ValueError while generating its disk. The scenario then built fixtures and
failed because the disk did not exist. The runner regression reproduces the
status loss with a failing producer and an inert build boundary.

Expected and actual behavior

Directory and image creation failures must stop preparation with their original
status. The original helper instead prints a disk path after the failed command.
Partial or preexisting images must not admit a build after producer failure.

Environment and identity

Integration 32fb0a105c4bcd5ed96ab4ce5d9243259f683880, CI run 2645,
VM job 46952, attempt 1. The affected helper and scenario are unchanged in
a30ea110e4fd2e0502ab289b1c9a5fb7df3904df.

Evidence and prior checks

The original log records the generator exception before the scenario header,
followed by fixture work and block disk missing over two minutes later. Four
new runner controls expose the lost directory/generator status. The ACL encoding
error is a separate defect; this report does not attribute its cause or claim a
guest failure.

Tracking

Phase completion ·
Implementation PR

  • Preserve directory and generator failures before reporting a disk path.
  • Cover missing, partial and stale output, directory failure and valid paths.
  • Keep the original ACL fixture failure available for separate diagnosis.
## Summary Scenario preparation can continue after its block-image generator fails. It reports the intended image path and starts fixture work before a later missing disk error replaces the original failure. ## Reproduction [Run 2645](https://git.erikinkinen.fi/erix/integration/actions/runs/2645/jobs/1/attempt/1), `subsystem-ext4-acl-metadata-positive`, raised an ACL fixture `ValueError` while generating its disk. The scenario then built fixtures and failed because the disk did not exist. The runner regression reproduces the status loss with a failing producer and an inert build boundary. ## Expected and actual behavior Directory and image creation failures must stop preparation with their original status. The original helper instead prints a disk path after the failed command. Partial or preexisting images must not admit a build after producer failure. ## Environment and identity Integration `32fb0a105c4bcd5ed96ab4ce5d9243259f683880`, CI run 2645, VM job 46952, attempt 1. The affected helper and scenario are unchanged in `a30ea110e4fd2e0502ab289b1c9a5fb7df3904df`. ## Evidence and prior checks The original log records the generator exception before the scenario header, followed by fixture work and `block disk missing` over two minutes later. Four new runner controls expose the lost directory/generator status. The ACL encoding error is a separate defect; this report does not attribute its cause or claim a guest failure. ## Tracking [Phase completion](https://git.erikinkinen.fi/erix/integration/issues/65) · [Implementation PR](https://git.erikinkinen.fi/erix/integration/pulls/12) - [x] Preserve directory and generator failures before reporting a disk path. - [x] Cover missing, partial and stale output, directory failure and valid paths. - [x] Keep the original ACL fixture failure available for separate diagnosis.
Author
Owner

Fixed in 4d4521ad. Directory and disk-generator errors now stop preparation with their original status before fixture builds begin. Partial or older images cannot hide a failed producer. The original ACL fixture exception remains available for a separate repair.

Fixed in `4d4521ad`. Directory and disk-generator errors now stop preparation with their original status before fixture builds begin. Partial or older images cannot hide a failed producer. The original ACL fixture exception remains available for a separate repair.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:16 +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#127
No description provided.