Skip to main content
← Back to list
01Issue
BugShippedExtensionsPublicTeam
AssigneesNone

Relationships

↔ sibling #4776

#4773 @swamp/cfgmgmt systemd: a failed enable or start does not fail the step

Opened by randybias · 11/15/2026· Shipped 11/15/2026

Versions: @swamp/cfgmgmt 2026.11.01.1, swamp 20261114.210101.0.

What happens: an error from enable or start is collected and reported in the method's result, but the step does not fail.

What we expected: a failed enable or start fails the step, as the extension's description says convergence failures do ("Convergence failures propagate as step failures").

Shortest reproduction:

  1. Define a unit with an invalid ExecStart and ensure it running.
  2. Run apply. The result reports the failure, and the step and the workflow carry on as successful.

Why it matters: a silent failed start looks like success in a workflow.

Upstream repository: https://github.com/swamp-club/swamp-extensions

Environment

  • Extension: @swamp/cfgmgmt@2026.11.01.1
  • swamp: 20261114.210101.0-sha.537e03d1
  • OS: linux (x86_64)
  • Deno: 2.9.8
  • Shell: /bin/bash
02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPEDLINKED+ 5 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

11/15/2026, 10:09:30 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 linked sibling of #477611/15/2026, 7:37:52 PM
Editable. Press Enter to edit.

system commented 11/15/2026, 12:44:29 PM

Classified automatically when this issue was filed.

  • Source: Extensions

If you feel this classification is incorrect, add a ripple to tell us so.

stack72 commented 11/15/2026, 10:09:35 PM

Thanks @randybias for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Sign in to post a ripple.