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

fail to specify several connect stanzas per group #6646

Closed
err0r500 opened this issue Nov 7, 2019 · 4 comments · Fixed by #6653
Closed

fail to specify several connect stanzas per group #6646

err0r500 opened this issue Nov 7, 2019 · 4 comments · Fixed by #6653
Assignees
Labels
Milestone

Comments

@err0r500
Copy link

err0r500 commented Nov 7, 2019

Nomad version

Nomad v0.10.1 (829f9af35c77d564b3dab74454eeba9bf25e2df8)

Operating system and Environment details

ubuntu bionic

Issue

Fail to specify several connect stanza per group

Reproduction steps

submit the job below (it passes the validation) and you'll receive this error :

failed to setup alloc: pre-run hook "group_services" failed: invalid Consul Connect configuration for service "tcp": No Connect port defined for service "tcp"

Job file (if appropriate)

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

  group "activemq" {
    network {
      mode = "bridge"
    }

    service {
      name = "activemq-web"
      port = "8161"
      connect {
        sidecar_service {}
      }
    }

    service {
      name = "tcp"
      port = "61616"
      connect {
        sidecar_service {}
      }
    }

    service {
      name = "stomp"
      port = "61613"
      connect {
        sidecar_service {}
      }
    }

    task "activemq" {
      driver = "docker"

      config {
        image = "webcenter/activemq"
      }
    }
  }
}
@tgross tgross added this to Needs Triage in Nomad - Community Issues Triage via automation Nov 7, 2019
@nickethier
Copy link
Member

Hey @err0r500 I was able to reproduce this and should have a fix shortly. Thanks for reporting!

@nickethier nickethier self-assigned this Nov 8, 2019
@nickethier nickethier moved this from Needs Triage to Triaged in Nomad - Community Issues Triage Nov 8, 2019
@nickethier nickethier moved this from Triaged to In Progress in Nomad - Community Issues Triage Nov 8, 2019
@nickethier nickethier added this to the 0.10.2 milestone Nov 8, 2019
Nomad - Community Issues Triage automation moved this from In Progress to Done Nov 8, 2019
@sibblegp
Copy link

sibblegp commented Jan 4, 2020

Hello! I pasted this directly into Nomad and the connect proxies won't start with a "Base ID" error. Running Nomad 0.10.2 and Consul 1.6.2. This is preventing us from moving forward. Would love some help. Thanks!

@kneufeld
Copy link
Contributor

I just wanted to say thanks for fixing this bug, I was running 0.10.1 when I hit it and was about to lose my mind but a quick upgrade and I'm all good. I ❤️ the hashi stack.

@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 Nov 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants