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

constraint backwards compatibility breakage #3130

Closed
ygersie opened this issue Aug 30, 2017 · 1 comment
Closed

constraint backwards compatibility breakage #3130

ygersie opened this issue Aug 30, 2017 · 1 comment

Comments

@ygersie
Copy link
Contributor

ygersie commented Aug 30, 2017

Nomad 0.6.2 is not compatible with old style declaration of constraints. If I have a distinct_hosts set like this:

    constraint {
        operator  = "distinct_hosts"
        value     = "true"
    }

I get the following plan result:

Error during plan: Unexpected response code: 500 (1 error(s) occurred:

* Constraint 1 validation failed: 1 error(s) occurred:

* Distinct hosts constraint doesn't allow RTarget. Got "true")

Either the documentation needs to be updated or this is a bug

dadgar added a commit that referenced this issue Aug 30, 2017
This PR removes validation that could break job backwards compatibility.
The targets are ignored so there is no side effects.

Fixes #3130
@github-actions
Copy link

github-actions bot commented Dec 8, 2022

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.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants