Skip to content

spawnctl 'deploy' can fail to find a spawnpoint even though 'scan' finds it #29

@gtfierro

Description

@gtfierro

Scan finds the spawnpoint fine

gabe@vonnegut:~/gabe-home-config/devices/emu2$ spawnctl scan gabe.home/sp
Discovered 1 SpawnPoint(s):
[alpha] seen 06 Sep 17 08:26 PDT (4.12s) ago at r0uT8QOzVuRiWIQTHWnEKUAl-JOgPXmy0gGfWMwddGQ=/sp
  Available Memory: 4032 MB, Available Cpu Shares: 3840
Metadata:
  • lastalive: 2017-09-06 15:26:49.334628494 +0000 UTC
  • Deployment: gabe.home
Services:
  • [tplink-kitchen] seen 06 Sep 17 08:26 PDT (4.04s) ago
      Memory: 7.94/64 MB, CPU Shares: ~43/256

But when I try to deploy on that spawnpoint, I get the following error

gabe@vonnegut:~/gabe-home-config/devices/emu2$ spawnctl deploy -u gabe.home/sp -c deploy.yaml -n emu2
[ERROR] Service deployment failed, Spawnpoint gabe.home/sp not found

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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