-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Example Redis deployment doesn't work on 1.3.0 without consul #12958
Comments
Ah, my bad. The example file contains a default service stanza without any |
Hi @mr-karan and thanks for raising this. This is an oversight on my part; Nomad 1.3 adds implicit constraints on task groups that utilise Consul service registration so they only get placed on nodes where Consul has been fingerprinted. I had not account for the non-short example job which includes this block. I think updating the default file to set the provider to Nomad is the correct choice, however, i'll raise this internally to gather opinions also. |
Closes #12927 Closes #12958 This PR updates the version of redis used in our examples from 3.2 to 7. The old version is very not supported anymore, and we should be setting a good example by using a supported version. The long-form example job is now fixed so that the service stanza uses nomad as the service discovery provider, and so now the job runs without a requirement of having Consul running and configured.
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Nomad version
Output from
nomad version
Operating system and Environment details
Issue
The example deployment from
nomad init
doesn't seem to run anymore on a single node Nomad acting as server+client (and no consul).Reproduction steps
nomad.hcl
Expected Result
As of 1.2.6 until yesterday this worked normally, so it should also continue to work on 1.3.0?
Actual Result
It seems to check whether consul is present on the client or not and errors out with
Constraint ${attr.consul.version} semver >= 1.7.0 filtered 1 node
When I go to the client attributes list (at http://localhost:4646/ui/clients/c8927149-1161-f27c-7079-1adce6d56697), I don't see any
consul
block. Which makes sense because thisconsul
block doesn't exist in the agent config file. The same issue happens even if I runnomad agent -dev
so the agent config is not the issue here, I suppose.Job file (if appropriate)
Same as
nomad init
The text was updated successfully, but these errors were encountered: