Skip to content

fix: turn linger on during a linux system service install - #35169

Merged
bolichen97 merged 1 commit into
mainfrom
fix/34691-service-install-enables-linger
Nov 20, 2026
Merged

bolichen97 merged 1 commit into
mainfrom
fix/34691-service-install-enables-linger

Conversation

@bolichen97

@bolichen97 bolichen97 commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: A Linux system-service install turns linger on for the account the service runs as, so agent runtimes keep running after that account's last logout.

On Linux, kirocrew service install writes a system unit, but every agent runtime it starts runs under the service account's own user manager. systemd stops that manager at the account's last logout unless linger is on, so in-flight runtimes die and later ones start without their memory and fork-count ceilings. The install only printed a warning naming sudo loginctl enable-linger <user>, an extra manual sudo step, although the install already runs with root access (reported on Amazon Linux 2023 while following the remote crew on EC2 guide).

Why it matters

A system install is the path people pick so the gateway outlives their SSH or Session Manager session. Without linger that promise holds for the gateway but not for the work it runs: every logout kills agent runtimes, and only an install-time warning says so.

Not a goal

What changed (motivation → approach → change)

Observed: a system install leaves linger off, and agent runtimes die at the account's last logout. Root cause: the install only warned, even though it holds the root access the fix needs. Change, following the maintainer decision on the issue:

Case after a successful install Before After
Linger reported off warning naming the sudo command runs loginctl enable-linger <uid> itself and prints linger turned on for <user> ..., with sudo loginctl disable-linger <uid> to undo it
Linger not reported (an account with no login session, which logind does not track) nothing the same as the row above
That call fails — warning with loginctl's message and sudo loginctl enable-linger <uid> to run by hand; the install still succeeds
Linger already on, or no trusted loginctl nothing nothing
The account's uid does not resolve (the unit then bakes no user bus) warning when linger reads off nothing
systemd ships no per-user manager for the account warning when linger reads off, naming a command that cannot help there nothing

The step lives in service/linux_install.py (enable_service_account_linger) and is called by install_service() in service/controller.py where the warning was printed. It reuses the install's own privilege path, resolves loginctl from trusted system directories only, passes the numeric uid because root's name lookup can fail where the uid resolves, and asks the same per-user-manager question kirocrew doctor asks. It runs on every install, a re-install too, so linger turned off by hand comes back on and the printed line says so; kirocrew service uninstall leaves linger as it is. The CLI spec, the install, remote and EC2 guides, the facade's sudo-scope docstring and a new decision record under docs/decisions/ describe the behaviour.

Backwards compatibility

Compatible: the install's outcome, exit code and every earlier step are unchanged, and a host whose account already lingers sees no difference. The install does make one lasting host change it did not make before: with linger on, the account's user manager runs now and from every boot, with that account's other enabled user services and timers, and a re-install turns linger back on after someone turned it off by hand. The printed line names the undo command.

Removes nothing: linger_warning_for_service_account() stays on the kiro_crew.service.linux facade, deliberately, as part of its pre-split surface; the install stops printing its advice only where it now acts instead, or where the uid does not resolve or the host has no per-user manager, so the advice could not help.

Tests

  • test/test_service.py::TestLinuxUnitRendering::test_install_turns_linger_on_unless_it_is_on (linger reported off, and not reported): install_service() runs /usr/bin/loginctl enable-linger 1000 once and prints the turned-on line with the undo command.
  • test_a_failed_enable_names_the_command_to_run: a failed call returns the warning with loginctl's message and sudo loginctl enable-linger 1000.
  • test_linger_is_left_alone_when_it_has_nothing_to_do (already on, no per-user manager, no trusted loginctl, unresolved uid): no privileged call and no line to print.
  • test/test_service_controller.py::test_install_systemd_prints_the_linger_outcome: the install prints the turned-on line plainly and the failure after Warning:. The other install tests stub the step so no test can run a real loginctl.

Determinism: the 12 linger tests (-k linger over both files) passed 5 runs in a row at -n0 and once in a shuffled order (pytest-randomly 5.1.0, seed 3469134).

Proof: PROVEN test/test_service.py::TestLinuxUnitRendering::test_install_turns_linger_on_unless_it_is_on[reported-off], test/test_service.py::TestLinuxUnitRendering::test_install_turns_linger_on_unless_it_is_on[not-reported] (head 4de7c29)

Manual verification

The real install ran on a disposable host, base and head (next section). The read-only probe half ran against the live logind of an Amazon Linux 2023 host (systemd 252), the reporter's distribution: for an account that lingers, loginctl show-user <uid> -p Linger by numeric uid answers Linger=yes and the step has nothing to do; for a uid logind does not track, show-user fails, the probe reads that as unknown, and the step acts.

Real-machine verification

Machine: EC2 m7i.2xlarge, Ubuntu 24.04.5 LTS (systemd 255), x86_64, 8 vCPU / 30 GiB
Before (main 1308732): kirocrew service install, run by a fresh account with no login session and passwordless sudo -> kirocrew service installed and started. with no linger line; then loginctl show-user 1002 -p Linger -> User ID 1002 is not logged in or lingering, and systemctl is-active user@1002.service -> inactive
After (head 10ef8cb): the same command -> linger turned on for kcrmv, so agent runtimes keep running after its last logout. To turn it off: sudo loginctl disable-linger 1002; then Linger=yes and user@1002.service active. A second install prints no linger line, and kirocrew service uninstall leaves Linger=yes
Cleanup: linger turned off, the throwaway account, its sudo rule, the unit and the build removed (id finds no such user, no kirocrew* unit files, the linger directory empty); the instance is a disposable verification host with no inbound access, terminated once idle

Related Issues

Closes #34691

Sibling sweep

Swept: git grep -n "enable-linger" -- src/
Sibling: src/kiro_crew/doctor_checks/services.py:122 -- not affected -- doctor only reports and never changes the host, by design
Sibling: src/kiro_crew/pod/runtime.py:792 -- not affected -- the pod remedy runs without root, so it can only name the command
Sibling: src/kiro_crew/sandbox_cgroup.py:203 -- not affected -- a runtime log line from the unprivileged gateway
Sibling: src/kiro_crew/service/linux_install.py:231 -- not affected -- the SELinux refusal installs nothing; the operator sets up that user unit by hand
Sibling: src/kiro_crew/service/linux_unit.py:263 -- not affected -- the old advisory text, kept as facade surface

Pattern harvest

Not generalizable: one install step told the operator to run a command the installer already had the privilege to run; there is no code shape a rule could match.

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

Contribution License Agreement

@bolichen97
bolichen97 requested review from a team and KiroCrewCaptain as code owners November 11, 2026 07:49
@github-actions github-actions Bot added the readiness: checking Automated validation is still running label Nov 11, 2026
@github-actions

github-actions Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5) — ⏭️ skipped

Revision 4de7c2987b15b40ec196725e4662776b1e83dfcc touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Does not block merge.

@github-actions

github-actions Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5) — ✅ PASS

Premise-level review of 4de7c2987b15b40ec196725e4662776b1e83dfcc — why this exists and whether the shipped surface is the smallest honest version. Updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

First-Principles-Verdict: PASS

The fix acts at the cause: the install already has root, so it now enables linger instead of telling the user to. The only leftover is the advisory function it replaced, which now has no callers.

Not checked: maintainer decision on issue #34691 (the decision record cites it; I can't read GitHub here)

Notes

  • Item 7 — zero consumers: linger_warning_for_service_account had one production caller, controller.py (- linger_warning = linux.linger_warning_for_service_account()), and this diff removes it. I grepped linger_warning_for_service_account and got 0 non-test, non-facade-inventory hits. The description says it "stays on the kiro_crew.service.linux facade, deliberately". Subtraction: delete linux_unit.linger_warning_for_service_account, its facade export in service/linux.py, its two facade-inventory rows and its three tests in test/test_service.py.
  • Item 1 — the install's default behaviour changes without an RFC on the base. The new docs/decisions/ entry is added by this same diff. I treat this as a fix that completes what a system install already promises, so it is a note, not trigger (c).

What this change ships

Inventory (8 items) — 7 justified

Intent: keep agent runtimes alive after the service account logs out on a Linux system install — FIX.

  1. kirocrew service install turns linger on itself instead of only warning — justified
  2. Prints a "linger turned on" line with the undo command — justified
  3. A failed call warns with the manual command; the install still succeeds — justified
  4. A re-install turns linger back on after someone turned it off by hand — justified
  5. An account logind does not track is treated as linger off and gets linger turned on — justified
  6. Warning dropped when the uid doesn't resolve or the host has no per-user manager — justified
  7. The old advisory function stays on the facade with no callers — zero consumers
  8. CLI spec, install/remote/EC2 guides and a decision record describe the new behaviour — justified

[FIRST-PRINCIPLES-REVIEWED] 4de7c29

Description read

[DESCRIPTION-READ] 08fc674d9e66991b98a5bd176dc96ef2063eae9528c929d14dba239ea6aa4f7b

That sha256 names the PR description this verdict read. Recompute it with .github/scripts/pr-description-capture.sh; if it differs, the description changed after this verdict was formed and any finding drawn from the description is unproven.

@github-actions

github-actions Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5) — ✅ PASS

Design-level review of 4de7c2987b15b40ec196725e4662776b1e83dfcc — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Nothing blocks. The installer already has root, so it now enables linger itself instead of telling the operator to, and a failure only warns without changing the install outcome.

Notes

  • Every re-install turns linger back on, even if an operator switched it off on purpose, and there is no opt-out. The printed undo line is the only remedy, and it lasts only until the next install. If someone asks for an opt-out later, a service.* config key is the simplest fix.

[DESIGN-REVIEWED] 4de7c29

Description read

[DESCRIPTION-READ] f783930d951f208fe58a22d550f0934bb32e6506457357147f84787abd83ebeb

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review — ✅ no blocking findings

Reviewed 4de7c2987b15b40ec196725e4662776b1e83dfcc — this comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 4de7c29

Verdict parsed from the review's SHA-scoped output markers for commit 4de7c2987b15b40ec196725e4662776b1e83dfcc.

False positive or not applicable? A repository writer can comment:
/ai-review override fable 4de7c2987b15b40ec196725e4662776b1e83dfcc false-positive: <reason, 20 to 500 characters>

@github-actions

github-actions Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review — ✅ no blocking findings

GPT 6.1 completed its review of 4de7c2987b15b40ec196725e4662776b1e83dfcc and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 4de7c29

False positive or not applicable? A repository writer can comment:
/ai-review override gpt 4de7c2987b15b40ec196725e4662776b1e83dfcc false-positive: <reason, 20 to 500 characters>

@KiroCrewCaptain

KiroCrewCaptain commented Nov 11, 2026 •

Copy link
Copy Markdown
Collaborator

Code change approver recommendation: Approve

Why: the decider estimates a 12% chance that this change introduces a defect, within the 12% limit for approving on its own, and every check passes.

The PR replaces the install-time linger warning with a privileged loginctl enable-linger <uid> call that runs only after a successful system install. loginctl comes from trusted system directories, the call goes through the existing _sudo_run path (which never raises), and a failure only warns: the install still exits 0. The step is skipped when linger is already on, no trusted loginctl exists, the uid does not resolve, or the host has no per-user manager. Tests cover each case through facade patching, which does reach linux_install's new imports. Every other install_service() test stubs the step. The spec and guides were updated in the same commit. Uninstall leaving linger on is a stated non-goal and is documented. The First Principles lane's block is procedural: the maintainer's decision is on the issue, a maintainer recorded an owner-decision release on the earlier head, and the PR adds the decision record. The CI failures are an unrelated timing test and lanes that failed on rate limits.

An automated recommendation, not a review: a maintainer still decides. It approves on its own only when the estimated chance of a defect is at most 12% and the change has at most 400 changed lines. Decider v3c (217fe607) · commit c872012604 · 289 changed lines. If this recommendation is wrong, reply here: replies are how the approver is evaluated.

@bolichen97
bolichen97 enabled auto-merge (squash) November 11, 2026 08:18
@bolichen97

Copy link
Copy Markdown
Contributor Author

[operator: bolichen97] Analyze (python) (CodeQL) is red on this head at its SARIF upload step with API rate limit exceeded for installation (run 42982300878). The same step fails the same way on main (run 42982645187) and on other open PRs from the same window, so it is not this diff. The shared token quota behind it is tracked in #28761. The failed job gets one rerun once the quota recovers; there is no code change for it here.

@github-actions github-actions Bot added readiness: action required A blocking check or review needs attention and removed readiness: checking Automated validation is still running labels Nov 11, 2026
buluoray
buluoray previously approved these changes Nov 11, 2026

@buluoray buluoray left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve on 59ad081. Linux system install now runs loginctl enable-linger <uid> itself through the existing privilege path, with loginctl from trusted system dirs, skipping when linger is on, no per-user manager, or uid unresolved; a failure only warns and the install still succeeds. Decisive lines: src/kiro_crew/service/linux_install.py:434-469 (enable_service_account_linger), src/kiro_crew/service/controller.py:191-193 (call site, non-fatal print)

@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 11, 2026
@bolichen97
bolichen97 force-pushed the fix/34691-service-install-enables-linger branch from 59ad081 to 0d1a559 Compare November 11, 2026 20:02
@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in docs/decisions/README.md since this head went green (65bdd09 -> 23b63d2); CI re-running. The branch conflicted there because main and this PR each appended a row to the decision index; both rows are kept. The PR's own change is unchanged apart from a two-line comment in service/controller.py, now 0d1a559.

[operator: bolichen97]

@bolichen97

bolichen97 commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor Author
  • Manual verification skipped for a branch CI cannot exercise span=d2063d8e2536

Rebutted: the deciding half now has live evidence, under Manual verification: on Amazon Linux 2023 (systemd 252), loginctl show-user <uid> -p Linger by numeric uid answers Linger=yes for a lingering account, and the step does nothing.
For a uid logind does not track, show-user fails, the probe returns unknown and user_manager_unit names user@<uid>.service, so "not reported" is acted on, as the unit tests assert.
That loginctl documents enable-linger as taking user names or numeric UIDs; the one privileged call is the command the old warning told operators to run, given the uid.
The re-install turning linger back on is stated under Backwards compatibility, with the undo command printed on every install.
The privileged call itself was not run here: a system install on this host would replace its own running service unit.
[operator: bolichen97]

@github-actions github-actions Bot removed the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 11, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

[operator: bolichen97] Design Review, First Principles Review, GPT 6.1 Review, Opus 5.5 Review, Publish readiness signal and Re-run Sensitive Change Review are red on 0d1a559 before reviewing anything: each failed fetching from the API with API rate limit exceeded for installation (for example Design Review run 43092766455). Every Design Review run on other open PRs since about 19:56Z fails the same way, so this is the shared CI token quota tracked in #28761, not this change. They get one rerun once the quota recovers.

@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 11, 2026
@bolichen97
bolichen97 force-pushed the fix/34691-service-install-enables-linger branch from 0d1a559 to cd4b4a4 Compare November 12, 2026 02:19
@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in docs/decisions/README.md since this head was cut (23b63d2 -> 26e8e9e); CI re-running. GitHub reported the branch as conflicting there because main and this PR each appended a row to the decision index; both rows are kept and the PR's own change is otherwise identical, now cd4b4a4. The reds on 0d1a559 were not this change: most jobs failed uploading artifacts while GitHub's artifact service answered with an HTML error page, and test/test_mcp_remote_transport.py::TestRewriter::test_a_listed_remote_entry_passes_through_unwrapped and ::test_a_malformed_type_does_not_abort_the_rewrite were red on main at the old base and are fixed there by #35541 and #35547, which this rebase picks up.

[operator: bolichen97]

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Nov 12, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor

Stale-PR cleanup check (2026-11-17): every lane except First Principles Review is fine on c872012, and the branch still merges cleanly with main. The First Principles BLOCK was released by an owner-decision override at a307d2d, but overrides apply to one commit only, so the rebased head needs the same override again from a maintainer (@bolichen97), citing #34691 (comment). The reviewer's side note (the unused linger_warning_for_service_account export) can be removed in the same push if you want. The cleanup will not post the override itself.

@github-actions github-actions Bot added the merge conflict Branch has merge conflicts with its base — author must resolve before merge label Nov 18, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

[operator: bolichen97] Thanks for the check. Since then GitHub reports the branch as conflicting with main (main's plain-word status prefixes landed in service/controller.py and the CLI spec); a rebased head is reviewed and goes out as soon as CI capacity frees up, and the First Principles ruling for that head goes in once the lane has run on it. On the side note: linger_warning_for_service_account stays, because test/campaign_facade_inventories/kiro_crew.service.linux.json pins it as one of the kiro_crew.service.linux facade's pre-split public names, so dropping it is a take-away change this PR does not need.

@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in src/kiro_crew/service/controller.py and docs/system-specs/modules/cli.md since this head went green (794afbb -> 1308732); CI re-running. GitHub reported the branch as conflicting: main's #38821 turned status emoji into plain words in both files, so the failed-linger line now starts with Warning: like the install's other warnings. The change is otherwise the same, and the body gains the real-machine run of the install, base and head.
[operator: bolichen97]

@bolichen97
bolichen97 force-pushed the fix/34691-service-install-enables-linger branch from c872012 to 10ef8cb Compare November 19, 2026 11:07
@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention merge conflict Branch has merge conflicts with its base — author must resolve before merge readiness: checking Automated validation is still running labels Nov 19, 2026
@bolichen97
bolichen97 force-pushed the fix/34691-service-install-enables-linger branch from 10ef8cb to 518a2f5 Compare November 19, 2026 13:42
@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in docs/decisions/README.md, docs/guides/install.md, docs/guides/remote-crew-on-ec2.md and docs/system-specs/modules/cli.md since this head was cut (1308732 -> 3b4e971); CI re-running.

The rebase applied cleanly and the PR's own change is unchanged: main touched none of the service code it edits. The only red on the previous head was the CodeQL JavaScript/TypeScript analysis, which failed while uploading its results on a GitHub API rate-limit error, not on any finding, and PR Readiness was red only because of it; the new run replaces it. The related service and doctor tests and the static checks pass on the rebased commit, and the Proof: line in the description was re-run against it.

[operator: bolichen97]

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Nov 19, 2026
@bolichen97

Copy link
Copy Markdown
Contributor Author

[operator: bolichen97] CI on 518a2f5 is red only where main is red or a known Windows flake hit; none of the failing tests reach the service install code this PR changes.

Check Failing test Status
Backend Tests (3.12, 1), Backend Tests (Windows) (4) test/test_process_cache_floor_ratchet.py::test_every_new_module_level_cache_has_a_per_test_reset (subagent_persistence.py::_NOT_DUE_MEMO) red on main too (run 44543577290); fix in #39479
Backend Tests (3.12, 7) test/test_source_link_github_case.py::TestOneChipPerObject::test_case_variants_collapse_to_one_chip red on main too; fix in #39475
Backend Tests (Windows) (8) test_the_bar_is_resent_only_when_its_items_change (pytest-timeout) known Windows flake, recorded in #39484
Backend Tests (Windows) (5) two TestCloneLifecycleAndExport tests in the auto-improvement app (watcher never reached exhausted) known Windows flake, already tracked
Coverage Gate none of its own fails closed because the shards above are red

This PR waits for #39479 and #39475 to land; the branch is then rebased onto main and CI re-runs. No change to this PR's code is needed for these reds.

A system install is chosen so work outlives the login session, but each
agent runtime runs under the service account's own user manager, which
systemd stops at the account's last logout unless linger is on. The
install only printed a warning naming the sudo command to run by hand.

The install now runs loginctl enable-linger for the account itself,
through the root access it already uses, unless logind reports linger on
or the host has no per-user manager for that account. It prints what it
did and how to undo it, and only warns, without failing the install,
when the call fails. Uninstall leaves linger as it is. The spec, the
install guides and a decision record describe the new behaviour.
@bolichen97
bolichen97 force-pushed the fix/34691-service-install-enables-linger branch from 518a2f5 to 4de7c29 Compare November 19, 2026 23:20
@bolichen97

Copy link
Copy Markdown
Contributor Author

Rebased: main moved in docs/decisions/README.md, docs/guides/remote-and-mobile.md and docs/system-specs/modules/cli.md since the last head (3b4e971 -> 82ee8d2); CI re-running.

The previous head was red only in tests that do not reach the service install code, and this rebase picks up main's fixes for four of them: the process-cache ratchet on the subagent tombstone sweep memo (#39479), the Windows poll in the auto-improvement watcher tests (#39545) and the Windows code-channel bar test (#39505, #39618). The fifth, a source-link chip count test that reads shared settings state, still has its fix open in #39475. The PR's own change is identical (the rebase applied cleanly with no edits), and the related service tests pass on the new head.

[operator: bolichen97]

@github-actions github-actions Bot added readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention labels Nov 20, 2026

@KiroCrewCaptain KiroCrewCaptain left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed head 4de7c29. On a Linux system service install, the new step turns on linger for the unit's account. It finds loginctl only in fixed system directories, runs it through the install's existing privilege path, and passes the resolved numeric uid. It does nothing when linger is already on, when the uid does not resolve, or when the host has no per-user manager. A root account is refused earlier in the install, so this step never runs for root. A failed call only prints a warning with the command to run, and the install result does not change. The service, controller, AppArmor, headless key, inherited env and facade-mirror suites pass on this head, so nothing blocks.

@bolichen97
bolichen97 merged commit c914ce6 into main Nov 20, 2026
99 of 100 checks passed
@bolichen97
bolichen97 deleted the fix/34691-service-install-enables-linger branch November 20, 2026 02:06
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Installing the gateway as a service on AL2023 leaves linger off. The installer warns that agent runtimes are killed at l

4 participants