[BUG] Writable FAT fixtures lack the required metadata catalog #133

Closed
opened 2026-10-15 23:37:55 +02:00 by erikinkinen · 5 comments
Owner

Summary

Both writable native CLI FAT scenarios fail redirection. Their image contains
plain FAT32, while the selected create/admit protocol requires a metadata catalog.

Reproduction

On Integration ab6a8d59491c132544490fbd1eda1ba56d6bfbb4, run
scripts/run-scenario.sh with either original scenario:

  • appliance-disk-image-initial-exsh-native-cli-time-fat-positive
  • appliance-disk-image-initial-exsh-native-cli-time-fat-truncate-positive

Both fail in CI 2702.

Expected and actual behavior

Creation and truncation should produce their original success markers and pass
the persisted payload and RTC timestamp checks. Instead, both print
exsh: redirection failed, followed by
ERIX_ROOTD:INITIAL_EXSH:NATIVE_CLI_TIME_FAILED:FAT_IO. The script exits 144;
the original 45-second serial watchdog later stops QEMU.

Environment and identity

The executor above selects runtime Integration 837b00cd, Rootd ff0bd1ef,
Fatd 01c8059e, Vfsd fe7b078a, and Exsh 8540bcf4. The release runtime image
uses the native CLI dev profile, x86_64 QEMU, a writable single-virtio GPT disk,
RTC 2035-04-05T06:07:08, and a 120-second QEMU limit. Existing cwd/resolver
owners and WRITE/CREATE_ENTRY ceilings apply. The last working graph is unknown.

Evidence and prior checks

The running-job log contains both failure contexts; it is not a terminal
result for the whole suite. The shared profile sets /boot flags to [], and
the builder formats plain FAT32. Fatd correctly refuses the native operation
without its catalog. The log does not expose the returned provider status.

Provision the existing catalog and undo tail during image construction, preserving
plain-media and read-only refusals. The status-endpoint IPC_NOT_FOUND failures
and extop pager fault in this run remain separate investigations.

Tracking

  • Provision the catalog before mounting, with focused fixture checks.
  • Pass both unchanged FAT guests, including the original media checks.

Implementation: Integration PR #12. Phase tracking: Integration #65.

## Summary Both writable native CLI FAT scenarios fail redirection. Their image contains plain FAT32, while the selected create/admit protocol requires a metadata catalog. ## Reproduction On Integration `ab6a8d59491c132544490fbd1eda1ba56d6bfbb4`, run `scripts/run-scenario.sh` with either original scenario: - `appliance-disk-image-initial-exsh-native-cli-time-fat-positive` - `appliance-disk-image-initial-exsh-native-cli-time-fat-truncate-positive` Both fail in [CI 2702][ci]. ## Expected and actual behavior Creation and truncation should produce their original success markers and pass the persisted payload and RTC timestamp checks. Instead, both print `exsh: redirection failed`, followed by `ERIX_ROOTD:INITIAL_EXSH:NATIVE_CLI_TIME_FAILED:FAT_IO`. The script exits 144; the original 45-second serial watchdog later stops QEMU. ## Environment and identity The executor above selects runtime Integration `837b00cd`, Rootd `ff0bd1ef`, Fatd `01c8059e`, Vfsd `fe7b078a`, and Exsh `8540bcf4`. The release runtime image uses the native CLI dev profile, x86_64 QEMU, a writable single-virtio GPT disk, RTC `2035-04-05T06:07:08`, and a 120-second QEMU limit. Existing cwd/resolver owners and WRITE/CREATE_ENTRY ceilings apply. The last working graph is unknown. ## Evidence and prior checks The [running-job log][ci] contains both failure contexts; it is not a terminal result for the whole suite. The shared profile sets `/boot` flags to `[]`, and the builder formats plain FAT32. Fatd correctly refuses the native operation without its catalog. The log does not expose the returned provider status. Provision the existing catalog and undo tail during image construction, preserving plain-media and read-only refusals. The status-endpoint `IPC_NOT_FOUND` failures and extop pager fault in this run remain separate investigations. ## Tracking - [x] Provision the catalog before mounting, with focused fixture checks. - [x] Pass both unchanged FAT guests, including the original media checks. Implementation: [Integration PR #12][pr]. Phase tracking: [Integration #65][phase]. [ci]: https://git.erikinkinen.fi/erix/integration/actions/runs/2702 [pr]: https://git.erikinkinen.fi/erix/integration/pulls/12 [phase]: https://git.erikinkinen.fi/erix/integration/issues/65
Author
Owner

2d3916ff provisions the existing FAT catalog inside the ESP. Boot files and the optional truncate seed are written before the catalog is built. The writable profile selects it explicitly; plain-media and read-only refusal rules are preserved.

The focused fixture and media-verifier checks pass. Both unchanged FAT guests, including their persisted payload and RTC checks, remain required before closing #133.

[`2d3916ff`](https://git.erikinkinen.fi/erix/integration/commit/2d3916ff88b91eeb21682d35c02062e5fe4eac34) provisions the existing FAT catalog inside the ESP. Boot files and the optional truncate seed are written before the catalog is built. The writable profile selects it explicitly; plain-media and read-only refusal rules are preserved. The focused fixture and media-verifier checks pass. Both unchanged FAT guests, including their persisted payload and RTC checks, remain required before closing [#133](https://git.erikinkinen.fi/erix/integration/issues/133).
Author
Owner

The first guest now reaches FAT_SCRIPT_OK, then the original media verifier rejects a raw creation date of 1980. The exact file's metadata catalog contains RTC-sourced timestamps inside the required window; the selected provider keeps those observations separate from raw FAT calendar fields. The verifier needs exact catalog-record, source and precision checks. The original run remains failed, and both full guest acceptance checks stay open.

The first guest now reaches `FAT_SCRIPT_OK`, then the original media verifier rejects a raw creation date of 1980. The exact file's metadata catalog contains RTC-sourced timestamps inside the required window; the selected provider keeps those observations separate from raw FAT calendar fields. The verifier needs exact catalog-record, source and precision checks. The original run remains failed, and both full guest acceptance checks stay open.
Author
Owner

The timestamp-verifier defect found by the first guest is now fixed in f0da4ac0, tracked separately in #134. Fresh create and truncate runs are being prepared; both acceptance items here remain open.

The timestamp-verifier defect found by the first guest is now fixed in `f0da4ac0`, tracked separately in [#134](https://git.erikinkinen.fi/erix/integration/issues/134). Fresh create and truncate runs are being prepared; both acceptance items here remain open.
Author
Owner

The fresh FAT create guest now passes on f0da4ac0, including the persisted media checks repaired in #134. The original failed runs remain recorded. The truncate guest is next.

The fresh FAT create guest now passes on `f0da4ac0`, including the persisted media checks repaired in [#134](https://git.erikinkinen.fi/erix/integration/issues/134). The original failed runs remain recorded. The truncate guest is next.
Author
Owner

Both unchanged native CLI FAT scenarios now pass on f0da4ac0. Creation persists fat-created; truncation persists the exact shorter fat-truncated payload. Both pass the original catalog identity, timestamp source/precision and RTC-window checks, with their original VM limits. The missing-catalog fixture regression is resolved.

Both unchanged native CLI FAT scenarios now pass on `f0da4ac0`. Creation persists `fat-created`; truncation persists the exact shorter `fat-truncated` payload. Both pass the original catalog identity, timestamp source/precision and RTC-window checks, with their original VM limits. The missing-catalog fixture regression is resolved.
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#133
No description provided.