[BUG] Image assembly loses the Boot-tool revision selected by its catalog #178

Open
opened 2026-10-23 19:39:03 +02:00 by erikinkinen · 1 comment
Owner

Summary

Integration prepares Boot-tool without passing the selected component catalog's
revision and source. Bootloader then uses its standalone default commit. The
owned Cargo source check rejects the resulting checkout before image assembly.

Reproduction

Use Integration 8501d3f52a8ae6019c9db9572da3c9577fab49f5 with its selected
Bootloader 508705ba42f2ee0c9fb45ce0c793a49ac7d85e15 and Boot-tool
50e22cb05ac2e2fd460ea83ca9c0e80fb484af98 sources. Run an image build through
package-appliance.sh or the VM wrapper. load_boot_tool_cargo_env invokes
prepare-boot-tool.py without --revision or --source; the standalone default
is bf90bcae1f20d2e9f05e87c961cad57a97697a22.

Expected and actual behavior

Every preparation and final verification should retain the same explicit
catalog revision and local source. Instead, the preparer selects a different
commit and the existing guard refuses it with checkout HEAD differs from the explicitly selected commit. Passing the selection only to the first call is
insufficient: Bootloader prepares and verifies the source again during assembly.

Environment and identity

Linux x86-64 host; Integration's canonical component catalog and original local
Git sources. No compiler or VM is needed to reproduce the preparation mismatch.
The standalone Bootloader default is valid for its own use and should remain
unchanged. No last working Integration revision has been established.

Evidence and prior checks

A local control using the original Bootloader preparer produces the default
checkout and reproduces the exact catalog refusal. Explicitly selecting the
catalog commit passes the same guard, a complete 34-file source comparison and
repeated final verification. CI 2945
contains the same refusal during VM scenarios, but its log omits the failing
checkout path; the local control establishes the preparation defect separately.

Tracking

Related: offline packaging
and PR 12.

  • Reproduce the standalone-default/catalog mismatch with genuine Git sources.
  • Retain the selected catalog, revision and source through both Cargo handoffs and later image preparation.
  • Cover invalid selections, failed setup, checkout layouts and repeated verification.
  • Get the affected CI image builds beyond source preparation.
## Summary Integration prepares Boot-tool without passing the selected component catalog's revision and source. Bootloader then uses its standalone default commit. The owned Cargo source check rejects the resulting checkout before image assembly. ## Reproduction Use Integration `8501d3f52a8ae6019c9db9572da3c9577fab49f5` with its selected Bootloader `508705ba42f2ee0c9fb45ce0c793a49ac7d85e15` and Boot-tool `50e22cb05ac2e2fd460ea83ca9c0e80fb484af98` sources. Run an image build through `package-appliance.sh` or the VM wrapper. `load_boot_tool_cargo_env` invokes `prepare-boot-tool.py` without `--revision` or `--source`; the standalone default is `bf90bcae1f20d2e9f05e87c961cad57a97697a22`. ## Expected and actual behavior Every preparation and final verification should retain the same explicit catalog revision and local source. Instead, the preparer selects a different commit and the existing guard refuses it with `checkout HEAD differs from the explicitly selected commit`. Passing the selection only to the first call is insufficient: Bootloader prepares and verifies the source again during assembly. ## Environment and identity Linux x86-64 host; Integration's canonical component catalog and original local Git sources. No compiler or VM is needed to reproduce the preparation mismatch. The standalone Bootloader default is valid for its own use and should remain unchanged. No last working Integration revision has been established. ## Evidence and prior checks A local control using the original Bootloader preparer produces the default checkout and reproduces the exact catalog refusal. Explicitly selecting the catalog commit passes the same guard, a complete 34-file source comparison and repeated final verification. [CI 2945](https://git.erikinkinen.fi/erix/integration/actions/runs/2945) contains the same refusal during VM scenarios, but its log omits the failing checkout path; the local control establishes the preparation defect separately. ## Tracking Related: [offline packaging](https://git.erikinkinen.fi/erix/integration/issues/172) and [PR 12](https://git.erikinkinen.fi/erix/integration/pulls/12). - [x] Reproduce the standalone-default/catalog mismatch with genuine Git sources. - [x] Retain the selected catalog, revision and source through both Cargo handoffs and later image preparation. - [x] Cover invalid selections, failed setup, checkout layouts and repeated verification. - [ ] Get the affected CI image builds beyond source preparation.
Author
Owner

Published b201fa5b.

Image entry points now retain the selected catalog through both Cargo handoffs and pass its exact Boot-tool revision and local source to later preparation and verification. All 13 handoff controls pass. The original preparer reproduces the default/catalog mismatch; explicit selection passes the complete 34-file source check and repeated verification. The existing HEAD guard remains unchanged.

The CI criterion remains open. A separate cancellation-test failure in #179 stopped the next host job before image assembly.

Published [b201fa5b](https://git.erikinkinen.fi/erix/integration/commit/b201fa5ba174cf0a95fd9a94f0ba9a3e9fe9d00c). Image entry points now retain the selected catalog through both Cargo handoffs and pass its exact Boot-tool revision and local source to later preparation and verification. All 13 handoff controls pass. The original preparer reproduces the default/catalog mismatch; explicit selection passes the complete 34-file source check and repeated verification. The existing HEAD guard remains unchanged. The CI criterion remains open. A separate cancellation-test failure in [#179](https://git.erikinkinen.fi/erix/integration/issues/179) stopped the next host job before image assembly.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:34:21 +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#178
No description provided.