andrewrothstein/ansible-consul

andrewrothstein.consul

Installs Consul

Requirements

See meta/main.yml

Role Variables

See defaults/main.yml

Dependencies

See meta/main.yml

Example Playbook

- hosts: servers
  roles:
    - andrewrothstein.consul

License

MIT

Author Information

Andrew Rothstein [email protected]

ansible-consul's Issues

Incompatible version formats

When attempting to install this role without specifying a version, the following error occurs:

- downloading role 'consul', owned by andrewrothstein
 [WARNING]: - andrewrothstein.consul was NOT installed successfully: Unable to compare role versions (v4.0.5, v3.2.1, 4.0.12, v4.0.4, v1.0.5, v3.0.6, v4.0.7, v4.0.0, v1.0.2, v1.0.3, v4.0.8, v4.0.2, v2.0.0, v4.0.11,
v4.0.10, v1.0.1, v3.1.1, v2.0.1, v3.0.7, v3.1.3, v3.0.1, v1.0.6, v4.0.3, v4.0.13, v3.0.3, v4.0.1, v1.0.7, v3.0.5, v3.1.2, v3.0.2, v1.0.4, v3.1.5, v4.0.6, v4.0.9, v3.0.0, v3.0.4, v3.1.0, v4.0.14, v1.0.0, v3.2.0,
v3.1.4, v3.2.2) to determine the most recent version due to incompatible version formats. Please contact the role author to resolve versioning conflicts, or specify an explicit role version to install.

Is it because 4.0.12 doesn't have the leading v?

States incorrect support for Trusty

The meta information says this role supports Ubuntu 14.04 LTS, Trusty. However, the task assumes systemd, and it wasn't until 15.04 that systemd replaced upstart in Ubuntu.

Envoy - Connect Sidecar Listening: connection refused

Hi there Andrew!

First, thanks and good jobs for the great ansible roles!

We're in the progress of setting up an automatic deployment of Consul (and Nomad) cluster. For a few days now, when deploying a Nomad job with a connect sidecar (using Envoy as defaults), we're encoutering a problem: Consul seems to have a Healtcheck problem with the Envoy sidecar attached to our services (systematically).

**Connect Sidecar Listening**
ServiceName my-service-sidecar-proxy CheckID service:_nomad-task-c46fr54c-5ec8-2136-5488-6fcs654b0f8c-group-my-service-my-service-interface-sidecar-proxy:2 Type tcp
Output **dial tcp 141.94.209.201:20538: connect: connection refused**

We have investigated the problem for 2 days, building the cluster anew everytime, but we don't seem to find a solution for now.

We've noticed you recently updated your Ansible role; so we'd like to ask if any trouble of the sort has been brought to your knowledge?

Thanks for all!

Best,