Skip to content

[stable34] fix(k8s): check daemon reachability by deploy id - #1027

Merged
oleksandr-nc merged 1 commit into
stable34from
backport/983/stable34
Sep 10, 2026
Merged

[stable34] fix(k8s): check daemon reachability by deploy id#1027
oleksandr-nc merged 1 commit into
stable34from
backport/983/stable34

Conversation

@backportbot

@backportbot backportbot Bot commented Sep 10, 2026

Copy link
Copy Markdown

Backport of #983

Warning, This backport's changes differ from the original and might be incomplete ⚠️

Todo

  • Review and resolve any conflicts
  • Review and verify the backported changes
  • Amend HEAD commit to remove the line stating to skip CI

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

Four call sites always ran the Docker ping: ExAppsPageService,
Settings\Admin, and the two DaemonConfigController endpoints behind the
admin UI's connection checks. On a kubernetes-install daemon that probes a
Docker Engine path HaRP does not serve, and it blocks until cURL times out
rather than failing fast — so a healthy daemon reads as unreachable, the
ExApp deploy button stays disabled and "Check Connection" reports failure.

Mirrors the dispatch SetupChecks\DaemonCheck already does.
@oleksandr-nc
oleksandr-nc marked this pull request as ready for review September 10, 2026 14:26
@oleksandr-nc
oleksandr-nc merged commit b2ef5a5 into stable34 Sep 10, 2026
53 of 54 checks passed
@oleksandr-nc
oleksandr-nc deleted the backport/983/stable34 branch September 10, 2026 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants