Host: a fail-start exception leaves the dotnet process running #618

Closed
opened 2026-10-08 02:31:15 -04:00 by dohertj2 · 1 comment
Owner

The R3-04 live gate found a fail-start validation error (e.g. unknown Cluster:Roles role) leaves dotnet alive instead of exiting; restart policies never see the failure, defeating the "fails host start" guarantee.
Sources: archreview/plans/STATUS.md:526-527 (tranche-1 follow-up 2).

  • Reproduce on docker-dev with an unknown role
  • Every validation/fail-start path exits non-zero (flush Serilog, then exit) with a test or scripted check

Filed 2026-10-08 by the pending/deferred-work sweep after the #562–#591 issue sweep.

The R3-04 live gate found a fail-start validation error (e.g. unknown `Cluster:Roles` role) leaves `dotnet` alive instead of exiting; restart policies never see the failure, defeating the "fails host start" guarantee. Sources: archreview/plans/STATUS.md:526-527 (tranche-1 follow-up 2). - [ ] Reproduce on docker-dev with an unknown role - [ ] Every validation/fail-start path exits non-zero (flush Serilog, then exit) with a test or scripted check _Filed 2026-10-08 by the pending/deferred-work sweep after the #562–#591 issue sweep._
Author
Owner

Resolved on master (413bc5c0, merge a6192159).

  • Reproduced: a fail-start exception left the process alive.
  • Program.cs now logs Fatal, flushes Serilog and exits non-zero on a failed start (tool paths that reuse the host builder are exempted). Pinned by FailStartExitTests, which spawns the built host as a child process with an invalid Akka seed and asserts a non-zero exit and a Fatal line within 60 s. Note: the repro/regression is process-level in the Host test, not a docker-dev run with an unknown role.
  • docs/Redundancy.md and docs/security.md updated.

Closed 2026-10-08 by the hardware-available issue sweep (master d898262c).

Resolved on master (413bc5c0, merge a6192159). - [x] Reproduced: a fail-start exception left the process alive. - [x] `Program.cs` now logs Fatal, flushes Serilog and exits non-zero on a failed start (tool paths that reuse the host builder are exempted). Pinned by `FailStartExitTests`, which spawns the built host as a child process with an invalid Akka seed and asserts a non-zero exit and a Fatal line within 60 s. Note: the repro/regression is process-level in the Host test, not a docker-dev run with an unknown role. - docs/Redundancy.md and docs/security.md updated. *Closed 2026-10-08 by the hardware-available issue sweep (master d898262c).*
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/lmxopcua#618