Skip to content

ENT-11189: Raised cf-apache.service start timeout to avoid PID-file race - #6371

Merged
larsewi merged 1 commit into
cfengine:masterfrom
larsewi:cf-apache-start-timeout
Sep 29, 2026
Merged

larsewi merged 1 commit into
cfengine:masterfrom
larsewi:cf-apache-start-timeout

Conversation

@larsewi

@larsewi larsewi commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

The earlier ENT-11189 fix only changed the masterfiles unit template. That template is used only with mpf_enable_cfengine_systemd_component_management, so hubs still ran this unit with the default 90 s start timeout. This adds the same TimeoutStartSec=300 here, keeping the unit in sync with the template.

Needs backport to 3.27.x and 3.24.x.

🤖 Generated with Claude Code

The ENT-11189 fix only changed the masterfiles template, which is used
only with mpf_enable_cfengine_systemd_component_management. Hubs use
this unit by default.

Ticket: ENT-11189
Changelog: Title
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Lars Erik Wik <lars.erik.wik@northern.tech>
@larsewi larsewi added the cherry-pick? Fixes which may need to be cherry-picked to LTS branches label Sep 29, 2026
@larsewi

larsewi commented Sep 29, 2026

Copy link
Copy Markdown
Contributor Author

@cf-bottom Jenkins please :)

@cf-bottom

Copy link
Copy Markdown

@larsewi
larsewi merged commit 56214bb into cfengine:master Sep 29, 2026
45 checks passed
@larsewi larsewi removed the cherry-pick? Fixes which may need to be cherry-picked to LTS branches label Sep 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants