[BUG] Worker archive permissions reject original VM metadata #164

Open
opened 2026-10-18 02:07:37 +02:00 by erikinkinen · 2 comments
Owner

Summary

The integration helper job can stop before the VM catalog when an archived worker scenario no longer matches its original file permissions. Git and tar have different archive/extraction defaults for root and ordinary users.

Reproduction

Use a committed scenario with mode 0644. Git's standard tar.umask=0002 archive records it as 0664. With process umask 0022, extract the same archive once with GNU tar's --same-permissions policy and once with --no-same-permissions. The first keeps 0664; the second yields 0644. Join each copied scenario to the original metadata plan without changing its bytes.

A regression control using real Git, GNU tar and the metadata hooks reproduces the mismatch and accepts the corrected transfer. It selects both extraction policies explicitly without requiring a privileged process or a VM.

Expected and actual behavior

Worker copies should preserve the selected committed source permissions while all original scenario mode, size and hash checks remain strict.

CI 2843 stopped in the cache-reuse host fixture. Its scenario returned zero, then metadata retention refused and the one-case helper summary failed. The real VM catalog did not start. The temporary original metadata ledger was not retained, so the exact differing field in that run is unknown; the permission difference reproduces the same retention failure, but does not establish which field differed in that earlier run.

Environment and identity

Integration revision fde8e900258c6e9ca4a9848ee8d7a904291c3090, Linux x86-64 host helper, rust:latest CI container. The affected path copies a committed Git archive into a worker directory. The failing host fixture builds no image and boots no VM.

Evidence and prior checks

The complete original CI log records successful worker blob verification followed by original VM metadata retention refused; VM status is unchanged and original scenario status=0.

The worker copy selects neither archive permissions nor extraction permissions. The original metadata plan compares full mode, byte count and SHA-256. The prepared repair makes transfer permissions explicit and retains the specific mismatched fields without changing original scenario outcomes. Six Python controls and both shell fixtures pass, including mode and body refusals that preserve the original zero and 73 statuses.

Tracking

  • Reproduce the permission mismatch with actual archive extraction and metadata hooks.
  • Publish a transfer that preserves 0644/0755 worker modes independently of archive configuration and extraction umask.
  • Publish the refusal diagnostics while keeping exact source checks and original statuses, including secondary diagnostic errors.
  • Reach the VM catalog in current component CI.

Related: Integration PR #12, Phase 6 tracking.

## Summary The integration helper job can stop before the VM catalog when an archived worker scenario no longer matches its original file permissions. Git and tar have different archive/extraction defaults for root and ordinary users. ## Reproduction Use a committed scenario with mode `0644`. Git's standard `tar.umask=0002` archive records it as `0664`. With process umask `0022`, extract the same archive once with GNU tar's `--same-permissions` policy and once with `--no-same-permissions`. The first keeps `0664`; the second yields `0644`. Join each copied scenario to the original metadata plan without changing its bytes. A regression control using real Git, GNU tar and the metadata hooks reproduces the mismatch and accepts the corrected transfer. It selects both extraction policies explicitly without requiring a privileged process or a VM. ## Expected and actual behavior Worker copies should preserve the selected committed source permissions while all original scenario mode, size and hash checks remain strict. [CI 2843](https://git.erikinkinen.fi/erix/integration/actions/runs/2843) stopped in the cache-reuse host fixture. Its scenario returned zero, then metadata retention refused and the one-case helper summary failed. The real VM catalog did not start. The temporary original metadata ledger was not retained, so the exact differing field in that run is unknown; the permission difference reproduces the same retention failure, but does not establish which field differed in that earlier run. ## Environment and identity Integration revision `fde8e900258c6e9ca4a9848ee8d7a904291c3090`, Linux x86-64 host helper, `rust:latest` CI container. The affected path copies a committed Git archive into a worker directory. The failing host fixture builds no image and boots no VM. ## Evidence and prior checks The complete original CI log records successful worker blob verification followed by `original VM metadata retention refused; VM status is unchanged` and `original scenario status=0`. The [worker copy](https://git.erikinkinen.fi/erix/integration/src/commit/fde8e900258c6e9ca4a9848ee8d7a904291c3090/scripts/lib/worker-source.sh) selects neither archive permissions nor extraction permissions. The original metadata plan compares full mode, byte count and SHA-256. The prepared repair makes transfer permissions explicit and retains the specific mismatched fields without changing original scenario outcomes. Six Python controls and both shell fixtures pass, including mode and body refusals that preserve the original zero and 73 statuses. ## Tracking - [x] Reproduce the permission mismatch with actual archive extraction and metadata hooks. - [x] Publish a transfer that preserves `0644`/`0755` worker modes independently of archive configuration and extraction umask. - [x] Publish the refusal diagnostics while keeping exact source checks and original statuses, including secondary diagnostic errors. - [ ] Reach the VM catalog in current component CI. Related: [Integration PR #12](https://git.erikinkinen.fi/erix/integration/pulls/12), [Phase 6 tracking](https://git.erikinkinen.fi/erix/integration/issues/65).
Author
Owner

The archive transfer and refusal diagnostics are published in 3be7eb07. CI 2846 is running; reaching the VM catalog remains open.

The archive transfer and refusal diagnostics are published in [3be7eb07](https://git.erikinkinen.fi/erix/integration/src/commit/3be7eb07c323f1860ff0ba89a88f8eb608a67970). [CI 2846](https://git.erikinkinen.fi/erix/integration/actions/runs/2846) is running; reaching the VM catalog remains open.
Author
Owner

The CI2846 live snapshot confirms that the host cache-reuse and worker-attestation fixtures pass. All observed worker-start messages belong to those temporary fixtures; the log does not yet establish that the complete VM catalog started, so the final criterion remains open.

Published 6a597b8f to correct the new guide’s Markdown line length without changing its wording.

The CI2846 live snapshot confirms that the host cache-reuse and worker-attestation fixtures pass. All observed worker-start messages belong to those temporary fixtures; the log does not yet establish that the complete VM catalog started, so the final criterion remains open. Published `6a597b8f` to correct the new guide’s Markdown line length without changing its wording.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:20 +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#164
No description provided.