The ansible-haproxy from entercloudsuite

ansible-haproxy's People

Contributors

Stargazers

Watchers

ansible-haproxy's Issues

The repository is no longer signed

Hi
I ran the playbook against an ubnutu server and I got the error below :

fatal: [[email protected]]: FAILED! => {"changed": false, "msg": "E:Failed to fetch https://download.docker.com/linux/ubuntu/dists/bionic/InRelease 403 Forbidden [IP: 143.204.101.42 443], E:The repository 'https://download.docker.com/linux/ubuntu bionic InRelease' is no longer signed."}

Could you please help me to resolve this issue ?

Dependancy Issue: KeepAlive

An issue arises when trying to use the example playbook. The version of keepalived (3.0.0) fails:

Ansible Version:

$ ansible --version
ansible 2.7.10
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/$USER/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 3.7.3 (default, Mar 26 2019, 21:43:19) [GCC 8.2.1 20181127]

Playbook:

$ cat playbooks/forwarder.yml
---
- hosts: all
  sudo: true
  roles:
    - name: entercloudsuite.haproxy 
      haproxy_conf: |
        listen web
          mode http
          bind *:80
          default-server port 80
          server web-0 1.1.1.1:80 check

Error:

TASK [oefenweb.keepalived : update configuration file] *************************
task path: /home/$USER/.ansible/roles/oefenweb.keepalived/tasks/main.yml:163
<127.0.0.1> ESTABLISH SSH CONNECTION FOR USER: vagrant
<127.0.0.1> SSH: EXEC ssh -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o
<127.0.0.1> (0, b'', b'')
fatal: [default]: FAILED! => {
    "changed": false,
    "msg": "AnsibleUndefinedVariable: 'dict object' has no attribute 'iteritems'"
}

I believe this is because of a structure change in the dependency module. However upgrading the KeepAlive module from 3.0.0 -> 3.2.0 (latests) seems to fix it. I'll put in a PR for that.