openstack ansible error when execute setup-openstack.yml

[Adnan Džaferović]

Hi,

I am trying to install latest release.. I succesfully pass setup-hosts.yml and setup-infrastructure.yml
When i execute setup-openstack.yml i got this error.

PLAY [Installation and setup of Keystone] ...

TASK [Set haproxy service state] ******************************************************************************************************************************************************************************
Friday 03 November 2017 08:32:16 +0100 (0:00:00.221) 0:00:10.838 *******
 [WARNING]: The loop variable 'item' is already in use. You should set the `loop_var` value in the `loop_control` option for the task to something else to avoid variable collisions and unexpected behavior.

failed: [infra1 -> 172.30.2.84] (item=infra1) => {"failed": true, "item": "infra1", "module_stderr": "Shared connection to 172.30.2.84 closed.\r\n", "module_stdout": "Traceback (most recent call last):\r\n File \"/tmp/ansible_wa8NVy/ansible_module_haproxy.py\", line 395, in <module>\r\n main()\r\n File \"/tmp/ansible_wa8NVy/ansible_module_haproxy.py\", line 389, in main\r\n ansible_haproxy.act()\r\n File \"/tmp/ansible_wa8NVy/ansible_module_haproxy.py\", line 343, in act\r\n state_before = self.get_state_for(self.backend, self.host)\r\n File \"/tmp/ansible_wa8NVy/ansible_module_haproxy.py\", line 289, in get_state_for\r\n data = self.execute('show stat', 200, False).lstrip('# ')\r\n File \"/tmp/ansible_wa8NVy/ansible_module_haproxy.py\", line 225, in execute\r\n self.client.connect(self.socket)\r\n File \"/usr/lib/python2.7/socket.py\", line 228, in meth\r\n return getattr(self._sock,name)(*args)\r\nsocket.error: [Errno 111] Connection refused\r\n", "msg": "MODULE FAILURE", "rc": 0}
failed: [infra1 -> 172.30.2.86] (item=infra3) => {"failed": true, "item": "infra3", "module_stderr": "Shared connection to 172.30.2.86 closed.\r\n", "module_stdout": "Traceback (most recent call last):\r\n File \"/tmp/ansible_qTLdlO/ansible_module_haproxy.py\", line 395, in <module>\r\n main()\r\n File \"/tmp/ansible_qTLdlO/ansible_module_haproxy.py\", line 389, in main\r\n ansible_haproxy.act()\r\n File \"/tmp/ansible_qTLdlO/ansible_module_haproxy.py\", line 343, in act\r\n state_before = self.get_state_for(self.backend, self.host)\r\n File \"/tmp/ansible_qTLdlO/ansible_module_haproxy.py\", line 289, in get_state_for\r\n data = self.execute('show stat', 200, False).lstrip('# ')\r\n File \"/tmp/ansible_qTLdlO/ansible_module_haproxy.py\", line 225, in execute\r\n self.client.connect(self.socket)\r\n File \"/usr/lib/python2.7/socket.py\", line 228, in meth\r\n return getattr(self._sock,name)(*args)\r\nsocket.error: [Errno 111] Connection refused\r\n", "msg": "MODULE FAILURE", "rc": 0}
failed: [infra1 -> 172.30.2.85] (item=infra2) => {"failed": true, "item": "infra2", "module_stderr": "Shared connection to 172.30.2.85 closed.\r\n", "module_stdout": "Traceback (most recent call last):\r\n File \"/tmp/ansible_wIGSSh/ansible_module_haproxy.py\", line 395, in <module>\r\n main()\r\n File \"/tmp/ansible_wIGSSh/ansible_module_haproxy.py\", line 389, in main\r\n ansible_haproxy.act()\r\n File \"/tmp/ansible_wIGSSh/ansible_module_haproxy.py\", line 343, in act\r\n state_before = self.get_state_for(self.backend, self.host)\r\n File \"/tmp/ansible_wIGSSh/ansible_module_haproxy.py\", line 289, in get_state_for\r\n data = self.execute('show stat', 200, False).lstrip('# ')\r\n File \"/tmp/ansible_wIGSSh/ansible_module_haproxy.py\", line 225, in execute\r\n self.client.connect(self.socket)\r\n File \"/usr/lib/python2.7/socket.py\", line 228, in meth\r\n return getattr(self._sock,name)(*args)\r\nsocket.error: [Errno 111] Connection refused\r\n", "msg": "MODULE FAILURE", "rc": 0}

[Jean-Philippe Evrard (jean-philippe-evrard)]

Is haproxy running on your node?

Could you paste your openstack_user_config on a pastebin to see if that would be the cause of the issue?

[Adnan Džaferović (adnandzaferovic)]

---
cidr_networks:
  container: 172.30.2.80/28
  tunnel: 172.30.131.16/28
  storage: 172.30.131.224/28

used_ips:
  - "172.30.2.81,172.30.2.91"
  - "172.30.131.17,172.30.131.23"
  - "172.30.131.225,172.30.131.232"

global_overrides:
  internal_lb_vip_address: 172.30.2.83
  #
  # The below domain name must resolve to an IP address
  # in the CIDR specified in haproxy_keepalived_external_vip_cidr.
  # If using different protocols (https/http) for the public/internal
  # endpoints the two addresses must be different.
  #
  external_lb_vip_address: 172.30.2.83
  tunnel_bridge: "br-vxlan"
  management_bridge: "br-mgmt"
  provider_networks:
    - network:
        container_bridge: "br-mgmt"
        container_type: "veth"
        container_interface: "ens160"
        ip_from_q: "container"
        type: "raw"
        group_binds:
          - all_containers
          - hosts
        is_container_address: true
        is_ssh_address: true
    - network:
        container_bridge: "br-vxlan"
        container_type: "veth"
        container_interface: "ens192"
        ip_from_q: "tunnel"
        type: "vxlan"
        range: "1:1000"
        net_name: "vxlan"
        group_binds:
          - neutron_linuxbridge_agent
    - network:
        container_bridge: "br-vlan"
        container_type: "veth"
        container_interface: "eth12"
        host_bind_override: "eth12"
        type: "flat"
        net_name: "flat"
        group_binds:
          - neutron_linuxbridge_agent
    - network:
        container_bridge: "br-vlan"
        container_type: "veth"
        container_interface: "eth11"
        type: "vlan"
        range: "1:1"
        net_name: "vlan"
        group_binds:
          - neutron_linuxbridge_agent
    - network:
        container_bridge: "br-storage"
        container_type: "veth"
        container_interface: "ens224"
        ip_from_q: "storage"
        type: "raw"
        group_binds:
          - glance_api
          - cinder_api
          - cinder_volume
          - nova_compute

###
### Infrastructure
###

# galera, memcache, rabbitmq, utility
shared-infra_hosts:
  infra1:
    ip: 172.30.2.84
  infra2:
    ip: 172.30.2.85
  infra3:
    ip: 172.30.2.86

# repository (apt cache, python packages, etc)
repo-infra_hosts:
  infra1:
    ip: 172.30.2.84
  infra2:
    ip: 172.30.2.85
  infra3:
    ip: 172.30.2.86

# load balancer
# Ideally the load balancer should not use the Infrastructure hosts.
# Dedicated hardware is best for improved performance and security.
haproxy_hosts:
  infra1:
    ip: 172.30.2.84
  infra2:
    ip: 172.30.2.85
  infra3:
    ip: 172.30.2.86

# rsyslog server
log_hosts:
  log1:
    ip: 172.30.2.90

###
### OpenStack
###

# keystone
identity_hosts:
  infra1:
    ip: 172.30.2.84
  infra2:
    ip: 172.30.2.85
  infra3:
    ip: 172.30.2.86

# cinder api services
storage-infra_hosts:
  infra1:
    ip: 172.30.2.84
  infra2:
    ip: 172.30.2.85
  infra3:
    ip: 172.30.2.86

# glance
# The settings here are repeated for each infra host.
# They could instead be applied as global settings in
# user_variables, but are left here to illustrate that
# each container could have different storage targets.
image_hosts:
  infra1:
    ip...

[Jean-Philippe Evrard (jean-philippe-evrard)]

Could you try running with external_lb_vip_address on a different address than your internal_lb_vip_address?

[Prerna Dembla (prerna.dembla)]

I am also facing this issue

[Jonathan Rosser (jrosser)]

We do not support running with internal and external VIP being the same address