Skip to content

spur nodes fails with "transport error / connection reset" when using custom ports #46

@amd-kmundiga

Description

@amd-kmundiga

Description

When running Spur with a custom controller port defined in /etc/spur/spur.conf, nodes successfully register with the controller, but spur nodes fails to retrieve partition/node information with a transport/connection error.

Controller logs:
Image

Compute node started with:
Image

WireGuard status:
Image

Steps to Reproduce

  • Start controller on custom port (6821)
  • Start compute node agents pointing to controller
  • Verify nodes register successfully in controller logs
  • Run: spur nodes
Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions