Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
gtfierro opened this issue Sep 6, 2017 · 1 comment

Comments

@gtfierro
Copy link
Member

gtfierro commented Sep 6, 2017

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
@gtfierro
Copy link
Member Author

gtfierro commented Sep 6, 2017

Can no longer reproduce on my machine...issue seems to have resolved itself, but I won't close this in case @jhkolb wants to investigate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant