Skip to content
This repository has been archived by the owner on Mar 18, 2021. It is now read-only.

Detect the configured DC from nomad or consul agent #51

Closed
acornies opened this issue Oct 3, 2018 · 1 comment
Closed

Detect the configured DC from nomad or consul agent #51

acornies opened this issue Oct 3, 2018 · 1 comment

Comments

@acornies
Copy link
Collaborator

acornies commented Oct 3, 2018

What are the steps to reproduce this issue?

  1. Deploy faas-nomad and gateway using a nomad/consul DC name other than dc1
  2. In the gateway UI or faas-cli, deploy a function from the store

What happens?

The function tries to deploy to DC dc1 instead of the configured DC from the nomad or consul agent

What were you expecting to happen?

The function is deployed with the agent's configured DC

Any logs, error output, etc?

No nodes were eligible for evaluation
No nodes are available in datacenter dc1

Any other comments?

Adding this issue for tracking, will tackle it shortly.

What versions of software are you using?

Operating System: Ubuntu 1604 x64

OpenFaaS Version: 0.9.3

Nomad Version: 0.8.4
@acornies acornies changed the title faas-nomad should detect the configured DC from nomad or consul Detect the configured DC from nomad or consul Oct 3, 2018
@acornies acornies changed the title Detect the configured DC from nomad or consul Detect the configured DC from nomad or consul agent Oct 3, 2018
@acornies acornies mentioned this issue Oct 18, 2018
Merged
@acornies
Copy link
Collaborator Author

acornies commented Nov 7, 2018

Resolved in v0.3.3

@acornies acornies closed this as completed Nov 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@acornies