[BUG] FAT time verifier reads calendar placeholders instead of catalog timestamps #134

Closed
opened 2026-10-16 00:53:40 +02:00 by erikinkinen · 3 comments
Owner

Summary

The native CLI FAT time verifier reads raw FAT calendar fields after the image
profile explicitly selects the original metadata catalog. It therefore rejects
a persisted native creation whose source-qualified catalog timestamps are valid
but whose offset-free FAT fields retain their canonical calendar placeholders.

Reproduction

Use Integration 2d3916ff88b91eeb21682d35c02062e5fe4eac34 and its selected
component catalog, then run the original scenario:

bash scripts/run-scenario.sh \
  tests/scenarios/appliance-disk-image-initial-exsh-native-cli-time-fat-positive.toml \
  components.toml

The scenario uses the original RTC base 2035-04-05T06:07:08 and persisted
fat-created payload. The related truncate and three touch modes share this
metadata-selected profile and the same raw-calendar observer assumption.

Expected and actual behavior

The post-image check should require the exact payload and target identity, clean
catalog/undo state, and the appropriate persisted source-qualified times within
the original RTC window. It must reject missing, stale or malformed metadata
without interpreting a raw FAT placeholder as UTC.

The original run exited 1 after the VM and marker checks passed, with:

FAT create time is outside the RTC window: 1980-01-01T00:00:00+00:00

The diagnostic's UTC-shaped value came from a raw FAT calendar helper. The held
target catalog instead contained HardwareRtc birth/access observations at
2035-04-05T06:07:46.690010373Z and modification/change observations at
06:07:54.434617615Z, each with one-second precision. The original failed run
remains failed; this observation does not grant retrospective guest acceptance.

Environment and identity

  • Executor: Integration 2d3916ff88b91eeb21682d35c02062e5fe4eac34.
  • Selected Fatd: 01c8059e44ecee7894415e1568b32382605b4d2f.
  • Selected Vfsd: fe7b078a13126691d59179889b6c3993e9056dc5.
  • Runtime Integration: 837b00cdffec23379484f34364d97ca35874aa04.
  • Runtime disk scenario, dev profile, selected FAT32 ESP metadata catalog.
  • Original QEMU 120-second and serial 45-second bounds; no oracle changes.
  • No last known working catalog-aware verifier revision is established.

Evidence and prior checks

The complete original status, serial output and post-run medium were retained.
The exact target's payload, LFN/short-entry binding, digest, size and catalog
record were correlated after all process owners retired. The selected provider
deliberately retains complete catalog observations independently of FAT calendar
range and timezone limitations. The proposed observer repair needs positive and
malformed/stale/wrong-object/source/precision/window controls before fresh guest
validation. This is distinct from the earlier missing-catalog write refusal,
status-endpoint failures and pager faults.

Tracking

Related fixture selection: Integration #133.
Integration work remains in PR #12
and the phase tracking issue #65.
Acceptance requires strict persisted-catalog verification and the two original
create/truncate scenarios on the actual published repair, with their original
payload, RTC bounds, deadlines and capture requirements.

  • Validate strict catalog identity/source/precision/window controls and source checks.
  • Pass the fresh original FAT create scenario on the published repair.
  • Pass the fresh original FAT truncate scenario on the published repair.
## Summary The native CLI FAT time verifier reads raw FAT calendar fields after the image profile explicitly selects the original metadata catalog. It therefore rejects a persisted native creation whose source-qualified catalog timestamps are valid but whose offset-free FAT fields retain their canonical calendar placeholders. ## Reproduction Use Integration `2d3916ff88b91eeb21682d35c02062e5fe4eac34` and its selected component catalog, then run the original scenario: ```sh bash scripts/run-scenario.sh \ tests/scenarios/appliance-disk-image-initial-exsh-native-cli-time-fat-positive.toml \ components.toml ``` The scenario uses the original RTC base `2035-04-05T06:07:08` and persisted `fat-created` payload. The related truncate and three touch modes share this metadata-selected profile and the same raw-calendar observer assumption. ## Expected and actual behavior The post-image check should require the exact payload and target identity, clean catalog/undo state, and the appropriate persisted source-qualified times within the original RTC window. It must reject missing, stale or malformed metadata without interpreting a raw FAT placeholder as UTC. The original run exited 1 after the VM and marker checks passed, with: ```text FAT create time is outside the RTC window: 1980-01-01T00:00:00+00:00 ``` The diagnostic's UTC-shaped value came from a raw FAT calendar helper. The held target catalog instead contained HardwareRtc birth/access observations at `2035-04-05T06:07:46.690010373Z` and modification/change observations at `06:07:54.434617615Z`, each with one-second precision. The original failed run remains failed; this observation does not grant retrospective guest acceptance. ## Environment and identity - Executor: Integration `2d3916ff88b91eeb21682d35c02062e5fe4eac34`. - Selected Fatd: `01c8059e44ecee7894415e1568b32382605b4d2f`. - Selected Vfsd: `fe7b078a13126691d59179889b6c3993e9056dc5`. - Runtime Integration: `837b00cdffec23379484f34364d97ca35874aa04`. - Runtime disk scenario, dev profile, selected FAT32 ESP metadata catalog. - Original QEMU 120-second and serial 45-second bounds; no oracle changes. - No last known working catalog-aware verifier revision is established. ## Evidence and prior checks The complete original status, serial output and post-run medium were retained. The exact target's payload, LFN/short-entry binding, digest, size and catalog record were correlated after all process owners retired. The selected provider deliberately retains complete catalog observations independently of FAT calendar range and timezone limitations. The proposed observer repair needs positive and malformed/stale/wrong-object/source/precision/window controls before fresh guest validation. This is distinct from the earlier missing-catalog write refusal, status-endpoint failures and pager faults. ## Tracking Related fixture selection: [Integration #133](https://git.erikinkinen.fi/erix/integration/issues/133). Integration work remains in [PR #12](https://git.erikinkinen.fi/erix/integration/pulls/12) and [the phase tracking issue #65](https://git.erikinkinen.fi/erix/integration/issues/65). Acceptance requires strict persisted-catalog verification and the two original create/truncate scenarios on the actual published repair, with their original payload, RTC bounds, deadlines and capture requirements. - [x] Validate strict catalog identity/source/precision/window controls and source checks. - [x] Pass the fresh original FAT create scenario on the published repair. - [x] Pass the fresh original FAT truncate scenario on the published repair.
Author
Owner

f0da4ac0 reads qualified catalog observations for all five FAT time modes and shares strict parsing with detached-record checks. It binds the persisted target, payload, timestamp source, precision and original RTC window. The host controls and source checks pass; fresh create and truncate guests remain required. The original failed guest result is retained.

`f0da4ac0` reads qualified catalog observations for all five FAT time modes and shares strict parsing with detached-record checks. It binds the persisted target, payload, timestamp source, precision and original RTC window. The host controls and source checks pass; fresh create and truncate guests remain required. The original failed guest result is retained.
Author
Owner

The fresh create guest passes on f0da4ac0, including the original success markers and strict persisted payload, catalog identity, timestamp source, precision and RTC-window checks. All three process owners shut down cleanly; the complete output and medium are retained. Truncate remains open.

The fresh create guest passes on `f0da4ac0`, including the original success markers and strict persisted payload, catalog identity, timestamp source, precision and RTC-window checks. All three process owners shut down cleanly; the complete output and medium are retained. Truncate remains open.
Author
Owner

The original FAT create and truncate scenarios both pass on f0da4ac0, including the strict persisted payload and source-qualified timestamp checks. The truncate result also preserves the seeded birth time and validates the independent raw-calendar seed fields. The original failed runs remain failed; these are fresh executions of the published repair.

The original FAT create and truncate scenarios both pass on `f0da4ac0`, including the strict persisted payload and source-qualified timestamp checks. The truncate result also preserves the seeded birth time and validates the independent raw-calendar seed fields. The original failed runs remain failed; these are fresh executions of the published repair.
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#134
No description provided.