[BUG] Read-only durability fixture omits a required host file #158

Open
opened 2026-10-17 14:49:54 +02:00 by erikinkinen · 0 comments
Owner

Summary

The read-only block-durability scenario selects the generic fs image, which
lacks the indexed-directory host file required by its guest verifier. The
existing fs-ext4-large-dir image supplies that file.

Reproduction

On Integration dacb2ae5, run
subsystem-block-durability-readonly-positive.toml. Its e2fs-fat-readonly
verifier requires HTREE_HOST_PATH and HTREE_HOST_DATA from
vfs_persistent.rs; the selected image leaves that directory empty.

Expected and actual behavior

The selected image must contain every file the guest reads. The generic image
cannot satisfy this proof. Keep the media and mounts read-only, the durability
barrier refusal, readiness checks and original timeout.

Environment and identity

The mismatch exists at Integration dacb2ae5; fixed by c94402fe. The repair
selects the populated
image and updates the scenario authority guard; it leaves the producer and guest
verifier unchanged.

Evidence and prior checks

Historical CI at efa366bc reached the mount marker and then exited 41 instead
of 33. Its log does not identify the failing file open. Host regression controls
exercise the real image producer, validate the GPT checksums and compare the
required file bytes; the generic image is the negative control. Both pass with
the scenario authority checks; the original VM case remains pending.

Tracking

Related: #12. Guest acceptance remains required.

  • Select the existing image containing the guest's required file.
  • Pass both real-producer controls and the scenario authority checks.
  • Pass the original read-only durability guest with all existing gates.
## Summary The read-only block-durability scenario selects the generic `fs` image, which lacks the indexed-directory host file required by its guest verifier. The existing `fs-ext4-large-dir` image supplies that file. ## Reproduction On Integration `dacb2ae5`, run `subsystem-block-durability-readonly-positive.toml`. Its `e2fs-fat-readonly` verifier requires `HTREE_HOST_PATH` and `HTREE_HOST_DATA` from `vfs_persistent.rs`; the selected image leaves that directory empty. ## Expected and actual behavior The selected image must contain every file the guest reads. The generic image cannot satisfy this proof. Keep the media and mounts read-only, the durability barrier refusal, readiness checks and original timeout. ## Environment and identity The mismatch exists at Integration `dacb2ae5`; fixed by `c94402fe`. The repair selects the populated image and updates the scenario authority guard; it leaves the producer and guest verifier unchanged. ## Evidence and prior checks Historical CI at `efa366bc` reached the mount marker and then exited 41 instead of 33. Its log does not identify the failing file open. Host regression controls exercise the real image producer, validate the GPT checksums and compare the required file bytes; the generic image is the negative control. Both pass with the scenario authority checks; the original VM case remains pending. ## Tracking Related: #12. Guest acceptance remains required. - [x] Select the existing image containing the guest's required file. - [x] Pass both real-producer controls and the scenario authority checks. - [ ] Pass the original read-only durability guest with all existing gates.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34: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#158
No description provided.