[BUG] Smoke image policy omits counted Launchd client storage #96

Closed
opened 2026-09-25 13:38:04 +02:00 by erikinkinen · 0 comments
Owner

Summary

The non-runtime image-policy producer still emits the 14-field Launchd tuple predating counted client storage. The current image consumer requires 16 fields. Both original Integration CI 1795 and 1796 stop 119 existing scenarios at image packaging with this error, before starting their VMs.

Reproduction

At Integration 4efc9d5d7aaee871f8021f74c65973e49edf5302, run from the repository root:

bash -euo pipefail -c 'source scripts/lib/deployment-state.sh; source scripts/lib/dynlink-image.sh; select_deployment_state_policy smoke; args=(); dynlink_append_launchd_capacity_args "$LAUNCHD_DEPLOYMENT_POLICY" args'

The original source deterministically exits 1. The strengthened deployment-policy regression also rejects that original producer with the same diagnostic. Its earlier smoke assertions checked only that the policy was nonempty, so the host suite missed the incompatible tuple.

Expected and actual behavior

The smoke policy must explicitly encode zero realm records, zero client records and zero plan bytes using the current 16-field tuple. Switching from runtime selection back to smoke must reset all three fields. The strict consumer must continue rejecting obsolete or partial tuples.

Instead the producer ends after the realm-record field and emits error: launchd LCH1 policy must contain exactly 16 values. Runtime configuration emits the complete tuple and is a separate path. No authority is gained by this packaging refusal.

Environment and identity

  • Original CI Integration revision: 8f4a1de524b7d7041beddf6029fecbf10b733ea9; the same defective producer remains at 4efc9d5d7aaee871f8021f74c65973e49edf5302.
  • Branch: feature/posix-compat.
  • Reproduction: host Bash policy selection and argument construction; no VM, toolchain build or additional guest grant is needed.
  • Relevant producer/consumer: scripts/lib/deployment-state.sh and scripts/lib/dynlink-image.sh.

Evidence and prior checks

Complete original CI review — 28 September 2026:

The smoke tuple correction in signed 447f642e4aaf4638a0997d0efc49e41dcd3fc79a is accepted. Its original CI1811 passes the complete workflow and all 492 scenarios. CI1812 passes 491/492, with the sole failure being the independent ext4 quota timeout tracked in issue 73; none of the 119 obsolete-policy rejections recurs. Both subsequent documentation-head runs CI1813/1814 pass their full workflows and 492 scenarios. The earlier producer correction, host regression and affected native VM now have matching full-CI evidence. This closes the policy-format defect only; unrelated reports remain open.

  • CI1814, 7db7aa53dee420d434add6f4980f4ea71236d399: All helper, catalog, canonical-image and subsequent workflow gates pass. Three complete logs contain 13,557,318 bytes and zero warning candidates. Rust and Markdown pass.
  • CI1813, 7db7aa53dee420d434add6f4980f4ea71236d399: All helper, catalog, canonical-image and subsequent workflow gates pass. Three complete logs contain 13,558,708 bytes and zero warning candidates. Rust and Markdown pass.
  • CI1812, 447f642e4aaf4638a0997d0efc49e41dcd3fc79a: The ext4 quota VM reaches its original 120-second deadline; every other catalog scenario passes. Three complete logs contain 13,946,086 bytes and zero warning candidates. Rust and Markdown pass.
  • CI1811, 447f642e4aaf4638a0997d0efc49e41dcd3fc79a: All helper, catalog, canonical-image and subsequent workflow gates pass. Three complete logs contain 13,562,177 bytes and zero warning candidates. Rust and Markdown pass.

Every one of the 119 failures in each run is the known policy-format issue: the older producer emits 14 fields while the consumer requires 16.

Admission, guarded preparation, private startup, configured clients, the pipeline descriptor script and ext4 quota all pass in both original runs. The selected Launchd 372ab70ea2ea1133a9bc3edb2cb621f9679b075d includes the configuration-carrier GRANT correction; the earlier client stall is absent. This corroborates the existing scoped closure of Launchd issue 10 and Integration issue 92. The unexplained older same-source pipeline pass/failure in issue 91 remains open; two later passes do not establish its cause. Original markers and deadlines are unchanged, and no unchanged job was rerun.

Each run has 119 exact obsolete LCH1 policy-length refusals: the older non-runtime producer emits 14 fields while the current image consumer requires 16. These remain classified under Integration issue 96, whose correction is in later signed 447f642e4aaf4638a0997d0efc49e41dcd3fc79a. The remaining failures are the known configuration-carrier stall in both runs and the independent pipeline descriptor recurrence in CI1800, tracked in issue 91. Later sources still require their own complete CI results.

Realm-capacity witness checkpoint — 25 September 2026: signed Exsh bc5cc8ac requires a third BEGIN to return canonical RESOURCE_EXHAUSTED while both selected realm records are occupied. The reply must be Unconfirmed with zero identity and receiver fields, and both original generations must still read as sealed. Every original byte-I/O, native exit, independent retirement, stale-selector and record-reuse check remains required. The three additional requests use the existing Launchd route and transfer no capability. The independent 99-call transcript rejects the preceding probe at its missing request; seven focused controls cover exact refusal, malformed replies, transport loss and unwanted receipts.

Seven development selections pass 987 tests each. All fourteen host/native build, strict Clippy and private-rustdoc configurations and 355 frame-checker controls pass without warnings. Seven release unit compilations retain the original silence failure, and six current native frame observations return incomplete reports with exit 1. Compiler issue 9 and frame issue 4 stay open. One bounded read-only compiler stack sample finds active LLVM inlining; it does not establish time attribution or a speedup. Original red-selector and Markdown-wrapping failures remain preserved.

Signed Docs e2d4ffc1 records the contract and reconciles resolved grant regressions. All 45 document controls pass; the complete 2,655-page manual builds without final warnings, all 491,488 word bounds pass and three affected/adjacent pages are visually reviewed. Original CI1091/1092 passes, with four complete logs reviewed through the final warning-free TeX pass.

Signed Integration bdd04a62 selects both original sources. All 174 helper and six profiler commands, strict orchestration Clippy and both unit selections, formatting, dependencies and Markdown pass: 187 commands, zero warnings. Both catalog policies, all 76 original signatures and complete transitive closure pass. The fresh structural audit covers 3,194 code files below 1,000 lines and 98 crate roots enforcing missing_docs; semantic authority closure remains separate. Fresh native capacity execution is pending with the original 120/45-second limits. No completion credit is added before that evidence.

Earlier guarded-fixture CI1797/1798 each passes 372/492 scenarios, including admission, preparation, startup and ext4 quota. All 120 failures are classified: 119 obsolete policy refusals tracked in Integration issue 96, and the original counted grant refusal resolved in Loaderd issue 5. Six complete logs total 25,636,311 bytes with zero warning candidates. No unchanged job was rerun; the later fixes still need their own full CI. Remaining supervisor loss, exhaustion/cleanup, external toolchain rebuilding and both complete EriX builds inside EriX remain required by the phase tracker.

The current consumer remains strict; the changed source adds no guest route or capability. Issue 96 retains the original deterministic rejection and both original CI runs' 119 packaging failures each.

All 174 helper and six profiler commands, fresh strict Clippy and both orchestration unit selections, formatting, dependency policy and Markdown pass: 187 commands, zero warnings. The existing subsystem-crash-reporting-positive VM now passes on this signed source with its original native exit, required/forbidden markers and 120/45-second limits. Its retained 119 artifacts include 194,161 serial bytes, empty QEMU stderr and zero image warnings. This is an affected original VM, not a replacement success criterion. Full original regression CI remains under observation; the separate guarded-fixture failures and ext4 quota timeout are not attributed to this correction.

The documentation status is signed as Integration 7db7aa53; only ROADMAP changes and all tested code/catalog bytes remain identical. Fresh formatting for both crates, Markdown, source policy and diff checks pass without warnings. Original corrected-source CI1811/1812 and status CI1813/1814 are queued.

The structural audit covers 76 repositories and 3,194 authored code files, all below 1,000 lines, with 264 full dependency pins and all 98 conventional/manifest crate roots enforcing missing_docs. This does not establish complete semantic authority closure. Completion remains 15.42%, 414/874 sub-items and 17/460 whole parents. Numeric CPU values, remaining loss/exhaustion, external toolchain rebuilding and both full EriX builds inside EriX remain required.

Original CI 1795 and original CI 1796 each report 369/492 passing VM scenarios and 123 failures. Complete logs attribute 119 failures per run to this policy-width rejection. The other three realm stalls and the ext4 quota timeout are separate failures; this report does not claim to fix them. Rust and Markdown jobs passed. Six complete logs total 26,838,134 bytes and contain zero build-warning candidates. No unchanged CI job was rerun.

Tracking

Integration PR and phase completion.

  • Reproduce the original producer rejection and attribute original CI failures.
  • Correct the smoke tuple without relaxing current-schema validation.
  • Cover fresh selection and reset through the real image argument consumer.
  • Pass host controls and an affected original VM with unchanged success gates.
  • Complete observation of the original full regression CI for the corrected source.
## Summary The non-runtime image-policy producer still emits the 14-field Launchd tuple predating counted client storage. The current image consumer requires 16 fields. Both original Integration CI 1795 and 1796 stop 119 existing scenarios at image packaging with this error, before starting their VMs. ## Reproduction At Integration `4efc9d5d7aaee871f8021f74c65973e49edf5302`, run from the repository root: ```bash bash -euo pipefail -c 'source scripts/lib/deployment-state.sh; source scripts/lib/dynlink-image.sh; select_deployment_state_policy smoke; args=(); dynlink_append_launchd_capacity_args "$LAUNCHD_DEPLOYMENT_POLICY" args' ``` The original source deterministically exits 1. The strengthened deployment-policy regression also rejects that original producer with the same diagnostic. Its earlier smoke assertions checked only that the policy was nonempty, so the host suite missed the incompatible tuple. ## Expected and actual behavior The smoke policy must explicitly encode zero realm records, zero client records and zero plan bytes using the current 16-field tuple. Switching from runtime selection back to smoke must reset all three fields. The strict consumer must continue rejecting obsolete or partial tuples. Instead the producer ends after the realm-record field and emits `error: launchd LCH1 policy must contain exactly 16 values`. Runtime configuration emits the complete tuple and is a separate path. No authority is gained by this packaging refusal. ## Environment and identity - Original CI Integration revision: `8f4a1de524b7d7041beddf6029fecbf10b733ea9`; the same defective producer remains at `4efc9d5d7aaee871f8021f74c65973e49edf5302`. - Branch: `feature/posix-compat`. - Reproduction: host Bash policy selection and argument construction; no VM, toolchain build or additional guest grant is needed. - Relevant producer/consumer: `scripts/lib/deployment-state.sh` and `scripts/lib/dynlink-image.sh`. ## Evidence and prior checks Complete original CI review — 28 September 2026: The smoke tuple correction in signed `447f642e4aaf4638a0997d0efc49e41dcd3fc79a` is accepted. Its original CI1811 passes the complete workflow and all 492 scenarios. CI1812 passes 491/492, with the sole failure being the independent ext4 quota timeout tracked in [issue 73](https://git.erikinkinen.fi/erix/integration/issues/73); none of the 119 obsolete-policy rejections recurs. Both subsequent documentation-head runs CI1813/1814 pass their full workflows and 492 scenarios. The earlier producer correction, host regression and affected native VM now have matching full-CI evidence. This closes the policy-format defect only; unrelated reports remain open. - [CI1814](https://git.erikinkinen.fi/erix/integration/actions/runs/1814), `7db7aa53dee420d434add6f4980f4ea71236d399`: All helper, catalog, canonical-image and subsequent workflow gates pass. Three complete logs contain 13,557,318 bytes and zero warning candidates. Rust and Markdown pass. - [CI1813](https://git.erikinkinen.fi/erix/integration/actions/runs/1813), `7db7aa53dee420d434add6f4980f4ea71236d399`: All helper, catalog, canonical-image and subsequent workflow gates pass. Three complete logs contain 13,558,708 bytes and zero warning candidates. Rust and Markdown pass. - [CI1812](https://git.erikinkinen.fi/erix/integration/actions/runs/1812), `447f642e4aaf4638a0997d0efc49e41dcd3fc79a`: The ext4 quota VM reaches its original 120-second deadline; every other catalog scenario passes. Three complete logs contain 13,946,086 bytes and zero warning candidates. Rust and Markdown pass. - [CI1811](https://git.erikinkinen.fi/erix/integration/actions/runs/1811), `447f642e4aaf4638a0997d0efc49e41dcd3fc79a`: All helper, catalog, canonical-image and subsequent workflow gates pass. Three complete logs contain 13,562,177 bytes and zero warning candidates. Rust and Markdown pass. Every one of the 119 failures in each run is the known [policy-format issue](https://git.erikinkinen.fi/erix/integration/issues/96): the older producer emits 14 fields while the consumer requires 16. Admission, guarded preparation, private startup, configured clients, the pipeline descriptor script and ext4 quota all pass in both original runs. The selected Launchd `372ab70ea2ea1133a9bc3edb2cb621f9679b075d` includes the configuration-carrier GRANT correction; the earlier client stall is absent. This corroborates the existing scoped closure of [Launchd issue 10](https://git.erikinkinen.fi/erix/launchd/issues/10) and [Integration issue 92](https://git.erikinkinen.fi/erix/integration/issues/92). The unexplained older same-source pipeline pass/failure in [issue 91](https://git.erikinkinen.fi/erix/integration/issues/91) remains open; two later passes do not establish its cause. Original markers and deadlines are unchanged, and no unchanged job was rerun. Each run has 119 exact obsolete LCH1 policy-length refusals: the older non-runtime producer emits 14 fields while the current image consumer requires 16. These remain classified under [Integration issue 96](https://git.erikinkinen.fi/erix/integration/issues/96), whose correction is in later signed `447f642e4aaf4638a0997d0efc49e41dcd3fc79a`. The remaining failures are the known configuration-carrier stall in both runs and the independent pipeline descriptor recurrence in CI1800, tracked in [issue 91](https://git.erikinkinen.fi/erix/integration/issues/91). Later sources still require their own complete CI results. Realm-capacity witness checkpoint — 25 September 2026: signed [Exsh bc5cc8ac](https://git.erikinkinen.fi/erix/exsh/commit/bc5cc8ac420e86a8632445fe7d7da47785e5ae0f) requires a third BEGIN to return canonical RESOURCE_EXHAUSTED while both selected realm records are occupied. The reply must be Unconfirmed with zero identity and receiver fields, and both original generations must still read as sealed. Every original byte-I/O, native exit, independent retirement, stale-selector and record-reuse check remains required. The three additional requests use the existing Launchd route and transfer no capability. The independent 99-call transcript rejects the preceding probe at its missing request; seven focused controls cover exact refusal, malformed replies, transport loss and unwanted receipts. Seven development selections pass 987 tests each. All fourteen host/native build, strict Clippy and private-rustdoc configurations and 355 frame-checker controls pass without warnings. Seven release unit compilations retain the original silence failure, and six current native frame observations return incomplete reports with exit 1. [Compiler issue 9](https://git.erikinkinen.fi/erix/exsh/issues/9) and [frame issue 4](https://git.erikinkinen.fi/erix/exsh/issues/4) stay open. One bounded read-only compiler stack sample finds active LLVM inlining; it does not establish time attribution or a speedup. Original red-selector and Markdown-wrapping failures remain preserved. Signed [Docs e2d4ffc1](https://git.erikinkinen.fi/erix/docs/commit/e2d4ffc1a1737ad21e682fef0ee622883e0c9536) records the contract and reconciles resolved grant regressions. All 45 document controls pass; the complete 2,655-page manual builds without final warnings, all 491,488 word bounds pass and three affected/adjacent pages are visually reviewed. Original CI1091/1092 passes, with four complete logs reviewed through the final warning-free TeX pass. Signed [Integration bdd04a62](https://git.erikinkinen.fi/erix/integration/commit/bdd04a62e0419061f33f850cabca0b6216994545) selects both original sources. All 174 helper and six profiler commands, strict orchestration Clippy and both unit selections, formatting, dependencies and Markdown pass: 187 commands, zero warnings. Both catalog policies, all 76 original signatures and complete transitive closure pass. The fresh structural audit covers 3,194 code files below 1,000 lines and 98 crate roots enforcing missing_docs; semantic authority closure remains separate. Fresh native capacity execution is pending with the original 120/45-second limits. No completion credit is added before that evidence. Earlier guarded-fixture CI1797/1798 each passes 372/492 scenarios, including admission, preparation, startup and ext4 quota. All 120 failures are classified: 119 obsolete policy refusals tracked in [Integration issue 96](https://git.erikinkinen.fi/erix/integration/issues/96), and the original counted grant refusal resolved in [Loaderd issue 5](https://git.erikinkinen.fi/erix/loaderd/issues/5). Six complete logs total 25,636,311 bytes with zero warning candidates. No unchanged job was rerun; the later fixes still need their own full CI. Remaining supervisor loss, exhaustion/cleanup, external toolchain rebuilding and both complete EriX builds inside EriX remain required by the [phase tracker](https://git.erikinkinen.fi/erix/integration/issues/65). The current consumer remains strict; the changed source adds no guest route or capability. [Issue 96](https://git.erikinkinen.fi/erix/integration/issues/96) retains the original deterministic rejection and both original CI runs' 119 packaging failures each. All 174 helper and six profiler commands, fresh strict Clippy and both orchestration unit selections, formatting, dependency policy and Markdown pass: 187 commands, zero warnings. The existing `subsystem-crash-reporting-positive` VM now passes on this signed source with its original native exit, required/forbidden markers and 120/45-second limits. Its retained 119 artifacts include 194,161 serial bytes, empty QEMU stderr and zero image warnings. This is an affected original VM, not a replacement success criterion. Full original regression CI remains under observation; the separate guarded-fixture failures and ext4 quota timeout are not attributed to this correction. The documentation status is signed as [Integration 7db7aa53](https://git.erikinkinen.fi/erix/integration/commit/7db7aa53dee420d434add6f4980f4ea71236d399); only ROADMAP changes and all tested code/catalog bytes remain identical. Fresh formatting for both crates, Markdown, source policy and diff checks pass without warnings. Original corrected-source CI1811/1812 and status CI1813/1814 are queued. The structural audit covers 76 repositories and 3,194 authored code files, all below 1,000 lines, with 264 full dependency pins and all 98 conventional/manifest crate roots enforcing missing_docs. This does not establish complete semantic authority closure. Completion remains 15.42%, 414/874 sub-items and 17/460 whole parents. Numeric CPU values, remaining loss/exhaustion, external toolchain rebuilding and both full EriX builds inside EriX remain required. [Original CI 1795](https://git.erikinkinen.fi/erix/integration/actions/runs/1795) and [original CI 1796](https://git.erikinkinen.fi/erix/integration/actions/runs/1796) each report 369/492 passing VM scenarios and 123 failures. Complete logs attribute 119 failures per run to this policy-width rejection. The other three realm stalls and the ext4 quota timeout are separate failures; this report does not claim to fix them. Rust and Markdown jobs passed. Six complete logs total 26,838,134 bytes and contain zero build-warning candidates. No unchanged CI job was rerun. ## Tracking [Integration PR](https://git.erikinkinen.fi/erix/integration/pulls/12) and [phase completion](https://git.erikinkinen.fi/erix/integration/issues/65). - [x] Reproduce the original producer rejection and attribute original CI failures. - [x] Correct the smoke tuple without relaxing current-schema validation. - [x] Cover fresh selection and reset through the real image argument consumer. - [x] Pass host controls and an affected original VM with unchanged success gates. - [ ] Complete observation of the original full regression CI for the corrected source.
erikinkinen added this to the Alpha 1 milestone 2026-10-30 09:39:18 +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#96
No description provided.