Repository navigation
Conversation
Remove the redundant recursive tmpfiles home rule. Existing d entries create, label, and constrain the home directories without walking container storage on every boot. The full SELinux denial gate is unchanged. Assisted-by: GPT-6.1 Sol via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
948274b
ℹ️ Sentinel notice — informational; author is trusted (owner), merge is not blockedHive flagged this PR (author @castrojo, head
Hive did not add the |
|
Verification: full CI unit suite 2880 passed, coverage 87%; all PR checks completed successfully (VM run). Full distinct-digest Utah lifecycle 43535082068 ran 16 passed / 8 skipped, with SELinux enforcing and its canary detected. The harness-induced systemd-tmpfiles AVC records went from 80 to 0. The run correctly remains red on 59 chcon mac_admin records from the image; the independent image-source repair is projectbluefin/utah#1203. Bootupd permissive-domain records remain warnings. No allowlist, policy, test, expected-output or check change was made. Native Dakota common evidence is only 1 passed / 117 skipped, and Firefox 0 passed / 1 skipped; those green checks do not prove comprehensive native coverage. Local full-suite fixture commits encounter the workstation Conventional Commits hook (3 failures); it was not disabled. |
|
@castrojo this PR is back in your court ( Failing checks:
Reply here or push a new head to this branch (same sign-off); CI and the review swarm re-run automatically and the PR returns to the normal path. Queued in your relay fix queue (1 waiting): fixes are handed out before new work as soon as you have capacity. |
|
Thanks, this was the right fix, and it showed that the |
The harness's /etc/tmpfiles.d/ci-user.conf began with a recursive `Z /var/home/bluefin-test` rule. Once the runner container is loaded, the home holds Podman storage, and every later boot made systemd-tmpfiles walk its hardlinks, producing systemd_tmpfiles_t -> proc_security_t denials on /proc/sys/fs/protected_hardlinks on every boot after the first (44 in lifecycle run 43510394355). The non-recursive `d` entries already create the home and .ssh and set their mode, owner and label. Found by castrojo in #1205 (whose utah lifecycle run 43535082068 has none of these denials once the rule is gone); redone here with a sign-off and a regression test, since #1205's commit has none. Assisted-by: Claude Opus 5.5 via Claude Code Claude-Session: https://claude.ai/code/session_01WcWm7qQa538Zjcuvv8jBtn Signed-off-by: Danathar <Danathar@users.noreply.github.com> Co-authored-by: Danathar <Danathar@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
What
Remove the redundant recursive
Ztmpfiles rule injected by the VM harness. The existingdrules create, constrain and relabel only the test home and.sshdirectories. No test files, fixtures, expected outputs, allowlists, policies, coverage thresholds or check conditions change.Why
In lifecycle run 43526643244, every executable Utah lifecycle scenario passed (16 passed, 8 skipped), but the SELinux gate failed. The VM serial log shows
systemd-tmpfileswalking Podman storage hardlinks beneath the test home on reboot; the recursive harness rule generatedsystemd_tmpfiles_tdenials reading/proc/sys/fs/protected_hardlinks. The nonrecursivedprimitive already performs the required directory setup. The matching harness skill records this ownership boundary.This does not suppress or claim to fix Utah's independent
chcondenials or bootupd's permissive-domain.bootc-aleph.jsonrecords. The full existing AVC gate and canary remain intact.Verification
change, rejected by this workstation's global Conventional Commits hook. Neither hooks nor tests were changed or disabled. CI runs the complete suite.just list-stubspassed. This repository has nojust checkrecipe or pre-commit configuration.bash -n; YAML parses. Raw actionlint with ShellCheck reports existing workflow warnings, retained in the report rather than suppressed.systemd-tmpfiles --createapplied twice to private home/.ssh directories with hardlinked container contents: home/.ssh remain 0700 and nested container file modes/ownership remain unchanged.Attribution is included in the commit trailers. No forced release, hold closure, self-approval or merge is requested.