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

consul block inside group is silently ignored on Nomad OSS #11422

Closed
lgfa29 opened this issue Nov 1, 2021 · 1 comment · Fixed by #11423
Closed

consul block inside group is silently ignored on Nomad OSS #11422

lgfa29 opened this issue Nov 1, 2021 · 1 comment · Fixed by #11423
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/consul type/bug

Comments

@lgfa29
Copy link
Contributor

lgfa29 commented Nov 1, 2021

Nomad version

1.2.0-beta1

Operating system and Environment details

MacOS

Issue

consul is an Enterprise-only field but if a job is registered against an OSS cluster the job registration works without error and the field is silently ignored.

Reproduction steps

  1. Run job with consul block against an OSS cluster
  2. Retrieve job spec from the Nomad API

Expected Result

An error message is thrown similar to what happens with multiregion.

$ nomad run example.nomad
Error submitting job: Unexpected response code: 500 (1 error occurred:
        * Multiregion jobs are unlicensed.

)

Actual Result

Job is registered, but field is silently ignored.

Job file (if appropriate)

job "example" {
  datacenters = ["dc1"]

  group "cache" {
    consul {
      namespace = "dev"
    }

    task "redis" {
      driver = "docker"
      config {
        image = "redis:3.2"
      }
    }
  }
}
@lgfa29 lgfa29 added the type/bug label Nov 1, 2021
@lgfa29 lgfa29 added stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/consul labels Nov 1, 2021
@github-actions
Copy link

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 Oct 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
stage/accepted Confirmed, and intend to work on. No timeline committment though. theme/consul type/bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant