95 lines
5.3 KiB
Markdown
95 lines
5.3 KiB
Markdown
# APT host reboot evidence and the configured historical attempt
|
|
|
|
Actual result on 2026-11-13: the Cloud Linux VM's historical configure attempt
|
|
`33775478-15b0-46ec-b059-44f500dbb0b6` is now **failed** with
|
|
`APT_RECOVERY_CONFIGURED_ACCEPTANCE_REBOOT_FLAG_VERIFIED`. The package effect
|
|
completed, but this is a failed acceptance, not an accepted installation.
|
|
Normal signed RootSync closed the same attempt; no new job or package command
|
|
was used for this classification. The notebook remains development-only and
|
|
the server remains `discovery.ease-technologies.de`.
|
|
|
|
## Why the earlier result was unknown
|
|
|
|
The separately WebUI-approved configure-only job configured fixture `1.0` and
|
|
returned APT exit 0 with the expected hook armed. Its private sandbox reported
|
|
no reboot marker. The parent observed the host's reboot-required marker, so
|
|
the previous provider returned `FIXTURE_UNEXPECTED_REBOOT_REQUIRED` and kept
|
|
the attempt unknown. That provider had not measured the host flag before the
|
|
effect. A private `/run` observation cannot establish the host's earlier state.
|
|
The marker's timestamp does not replace that missing measurement.
|
|
|
|
The original failed unpacked attempt
|
|
`31ef5e5e-5dbd-4428-a9a1-cbd15de2f5a0`, its partial proof
|
|
`dc3bf3870ea77c12f9291bac712c53ae72194eaec980a8646155a7fb5c0dbe21`,
|
|
both bootstrap tombstones and the configure attempt marker remain intact.
|
|
Neither an install acceptance nor a recovery acceptance was created for 337.
|
|
|
|
## New provider contract
|
|
|
|
Spec 1.13 permits a fully verified package result with an already pending host
|
|
reboot. For future mutating jobs, the parent now seals the host flag and boot ID
|
|
before entering the sandbox. Native prechecks schema 2 binds that record's hash.
|
|
After package verification the parent requires the same host flag and boot ID;
|
|
the child must still report no sandbox reboot marker. Both false/false and
|
|
true/true are valid. Either flag transition or a changed boot ID denies acceptance.
|
|
The reported `reboot_required` remains truthful, and
|
|
`reboot_required_introduced` is false. No reboot is initiated by these jobs.
|
|
|
|
Fresh planning exposes `host_reboot_required`. If it is true, the immutable
|
|
plan reason displayed for approval includes
|
|
“Host reboot already required; flag unchanged; no reboot in this job”.
|
|
Browser preparation and approval both verify the reason in the canonical
|
|
persisted plan payload. The new runtime uses the separate
|
|
`configured-reconcile-runtime/cases/` namespace and refuses to repeat the
|
|
historical configure-only operation.
|
|
|
|
The historical read-only verifier accepts only the exact saved 337 context,
|
|
signed action and old runtime bindings, original partial reference, 13 immutable
|
|
evidence files, APT 0/armed hook and original configure-only protocol. It checks
|
|
the complete installed snapshot twice, unchanged other packages, payload,
|
|
empty audit, idle locks, same boot and stable current host marker. It produces
|
|
a new failed classification with `effect_complete=true`,
|
|
`postconditions_passed=false` and `reboot_required=true`; it cannot manufacture
|
|
the missing before sample or a success record. See
|
|
[the helper contract](../tools/apt-transaction/HELPER-CONTRACT.md).
|
|
|
|
## Actually executed verification
|
|
|
|
All **81 Python tests passed without skips** in the offline, read-only Docker
|
|
development image as UID 1000. This included the real APT 2.6.2 protocol and
|
|
argument regressions with a fake dpkg collector, which changed neither host nor
|
|
copied package status. Targeted coverage includes both equal flag states,
|
|
both forbidden transitions, missing before evidence, changed boot, private
|
|
marker rejection, acceptance-record binding and strict historical failure
|
|
classification. These local tests supplement the native evidence below.
|
|
|
|
Python AST, browser JavaScript syntax and `git diff --check` also passed.
|
|
The qualified provider SHA256 is
|
|
`1dc0237dd8df9c9d22568bb1f6b047ede73bc2a5fca5c7fcedb7f24ab2a58b1e`;
|
|
the installed x86-64 helper is
|
|
`bbd2cf80a4e67b8a37ba3845c2bbed8b3c84d1eb01c1ac515a34577c8caa8ad0`
|
|
and agent is
|
|
`f40c7e2646e8122f5320c0909b0172ed8c749c218ec76b7ba3b8b397eb970671`.
|
|
|
|
The preserving native runtime upgrade completed. Its SSH response timed out;
|
|
an independent readback proved the completed report and all three installed
|
|
hashes, so it was not repeated. The probe and report certify runtime readiness,
|
|
not package acceptance. Normal RootSync then stored one append-only effect
|
|
reconciliation, preserved the original unknown bytes and closed the original
|
|
337 grant as failed. The actual Root ledger has **11 consumed, 0 unresolved,
|
|
0 faults**; central counts are **20 jobs, 20 outbox entries, 18 permits,
|
|
0 unresolved**. The earlier partial proof is unchanged and all forbidden
|
|
acceptance records remain absent.
|
|
|
|
Protected local witnesses, excluded from Git:
|
|
|
|
- `devstate/cloud-apt-recovery/configured-reconcile-runtime.json`
|
|
- `devstate/cloud-apt-recovery/configured-maintenance-completed-readback.json`
|
|
- `devstate/cloud-apt-recovery/capacity-recovery/configured-closure-3b7e66aba1b1495db1675eaab5117393.json`
|
|
- `devstate/cloud-apt-recovery/helper-configured-reconcile.json`
|
|
- `devstate/cloud-apt-recovery/agent-configured-reconcile.json`
|
|
|
|
At this checkpoint, the new provider's separately approved native `1.0`→`1.1`
|
|
upgrade and following no-change jobs remain outstanding. The historical
|
|
classification is not their acceptance and does not complete the Linux MVP.
|