Skip to content

NodeId or "Cannot find the service" errors when deploying using stack-deploy #124

Description

@rudokemper

Current Buggy or Suspicious Behavior

The last time we deployed, we kept running in these errors:

2026-06-02 16:39:30,473 - root - INFO - Creating new app: windmill-worker-native
2026-06-02 16:39:31,489 - root - INFO - Getting app info...
2026-06-02 16:39:31,495 - root - INFO - App build status retrieved
2026-06-02 16:39:32,495 - root - INFO - Getting app info...
2026-06-02 16:39:32,499 - root - INFO - App build status retrieved
2026-06-02 16:39:32,499 - root - INFO - App building finished...
2026-06-02 16:39:32,499 - root - INFO - App Definition Saved
2026-06-02 16:39:32,503 - root - INFO - App definitions are retrieved.
2026-06-02 16:39:32,503 - root - INFO - windmill-worker-native | Updating app info...
2026-06-02 16:39:32,519 - root - ERROR - No NodeId was found. Try again in a minute...

and

2026-06-02 17:08:18,173 - root - INFO - Creating new app: windmill-worker-native
2026-06-02 17:08:19,327 - root - INFO - Getting app info...
2026-06-02 17:08:19,334 - root - INFO - App build status retrieved
2026-06-02 17:08:20,334 - root - INFO - Getting app info...
2026-06-02 17:08:20,339 - root - INFO - App build status retrieved
2026-06-02 17:08:21,339 - root - INFO - Getting app info...
2026-06-02 17:08:21,343 - root - INFO - App build status retrieved
2026-06-02 17:08:22,343 - root - INFO - Getting app info...
2026-06-02 17:08:22,347 - root - INFO - App build status retrieved
2026-06-02 17:08:23,347 - root - INFO - Getting app info...
2026-06-02 17:08:23,352 - root - INFO - App build status retrieved
2026-06-02 17:08:24,352 - root - INFO - Getting app info...
2026-06-02 17:08:24,356 - root - INFO - App build status retrieved
2026-06-02 17:08:25,356 - root - INFO - Getting app info...
2026-06-02 17:08:25,361 - root - INFO - App build status retrieved
2026-06-02 17:08:26,361 - root - INFO - Getting app info...
2026-06-02 17:08:26,367 - root - INFO - App build status retrieved
2026-06-02 17:08:27,367 - root - INFO - Getting app info...
2026-06-02 17:08:27,375 - root - INFO - App build status retrieved
2026-06-02 17:08:28,375 - root - INFO - Getting app info...
2026-06-02 17:08:28,384 - root - INFO - App build status retrieved
2026-06-02 17:08:29,384 - root - INFO - Getting app info...
2026-06-02 17:08:29,388 - root - INFO - App build status retrieved
2026-06-02 17:08:30,389 - root - INFO - Getting app info...
2026-06-02 17:08:30,393 - root - INFO - App build status retrieved
2026-06-02 17:08:31,393 - root - INFO - Getting app info...
2026-06-02 17:08:31,397 - root - INFO - App build status retrieved
2026-06-02 17:08:32,398 - root - INFO - Getting app info...
2026-06-02 17:08:32,403 - root - INFO - App build status retrieved
2026-06-02 17:08:32,403 - root - INFO - App building finished...
2026-06-02 17:08:32,403 - root - INFO - App Definition Saved
2026-06-02 17:08:32,407 - root - INFO - App definitions are retrieved.
2026-06-02 17:08:32,407 - root - INFO - windmill-worker-native | Updating app info...
2026-06-02 17:08:32,412 - root - ERROR - Cannot find the service. Try again in a minute...

We concluded that the necessary step to resolve them was to reboot, as documented in ff99e77#diff-91daf193a2e7674abc74c3956f3e8fcedf18c78b7b8f4173200192036abcafa5:

sudo shutdown -r now

I encountered these errors again on a fresh deployment, and this time, rebooting did not solve the issue. I still encountered either flavor of this error 3 times before it finally worked (i.e. windmill-worker-native was able to install, and no other app had an issue).

Expected Behavior

We figure out a way to avoid these errors altogether as it's annoying to have to delete each service manually in the CapRover UI and start from scratch.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions