Error message appeared during openstack-ansible setup-infrastructure.yml execution
TASK [pip_install : Install PIP (fall back mode)] ***********************************************************************************************************************************************
Thursday 07 June 2018 10:51:49 +0000 (0:00:44.432) 0:19:25.544 *********
FAILED - RETRYING: Install PIP (fall back mode) (3 retries left).
FAILED - RETRYING: Install PIP (fall back mode) (2 retries left).
FAILED - RETRYING: Install PIP (fall back mode) (1 retries left).
fatal: [aio1_galera_container-db2a6e1e]: FAILED! => {"attempts": 3, "changed": false, "cmd": ["python", "/opt/get-pip.py", "--isolated", "--constraint", "http://<IP address>/gitweb/index.cgi?p=requirements.git;a=blob_plain;f=upper-constraints.txt;hb=6ea2d17f0a90985aa05c809c3e536abb7ea74b60", "pip", "setuptools", "wheel"], "delta": "0:00:09.335921", "end": "2018-06-07 10:52:34.012001", "failed": true, "rc": 1, "start": "2018-06-07 10:52:24.676080", "stderr": " Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f8062c27b10>: Failed to establish a new connection: [Errno -2] Name or service not known',)': /simple/pip/\n Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f8062c27990>: Failed to establish a new connection: [Errno -2] Name or service not known',)': /simple/pip/\n Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f8062c27a50>: Failed to establish a new connection: [Errno -2] Name or service not known',)': /simple/pip/\n Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f8062c27b50>: Failed to establish a new connection: [Errno -2] Name or service not known',)': /simple/pip/\n Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<pip._vendor.urllib3.connection.VerifiedHTTPSConnection object at 0x7f8062c27cd0>: Failed to establish a new connection: [Errno -2] Name or service not known',)': /simple/pip/\n Could not find a version that satisfies the requirement pip (from versions: )\nNo matching distribution found for pip", "stderr_lines": [" Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by
this error happened because haproxy dint start correctly as the TCP port 80 was not empty:
journalctl -u haproxy.service
Jun 07 10:50:01 ubuntu1604 systemd[1]: Started HAProxy Load Balancer.
Jun 07 10:50:01 ubuntu1604 haproxy-systemd-wrapper[20945]: haproxy-systemd-wrapper: executing /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -Ds
Jun 07 10:50:01 ubuntu1604 haproxy-systemd-wrapper[20945]: [ALERT] 157/105001 (20949) : Starting frontend horizon-redirect-front-1: cannot bind socket [<IP address>:80]
Jun 07 10:50:01 ubuntu1604 haproxy-systemd-wrapper[20945]: haproxy-systemd-wrapper: exit, haproxy RC=256
Jun 07 10:50:01 ubuntu1604 systemd[1]: haproxy.service: Service hold-off time over, scheduling restart.
Jun 07 10:50:01 ubuntu1604 systemd[1]: Stopped HAProxy Load Balancer.
Jun 07 10:50:01 ubuntu1604 systemd[1]: haproxy.service: Start request repeated too quickly.
Jun 07 10:50:01 ubuntu1604 systemd[1]: Failed to start HAProxy Load Balancer.
root@ubuntu1604:~# systemctl status haproxy.service
* haproxy.service - HAProxy Load Balancer
Loaded: loaded (/lib/systemd/system/haproxy.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Thu 2018-06-07 10:50:01 UTC; 11min ago
Docs: man:haproxy(1)
file:/usr/share/doc/haproxy/configuration.txt.gz
Process: 20945 ExecStart=/usr/sbin/haproxy-systemd-wrapper -f ${CONFIG} -p /run/haproxy.pid $EXTRAOPTS (code=exited, status=0/SUCCESS)
Process: 20943 ExecStartPre=/usr/sbin/haproxy -f ${CONFIG} -c -q (code=exited, status=0/SUCCESS)
Main PID: 20945 (code=exited, status=0/SUCCESS)
Jun 07 10:50:01 ubuntu1604 systemd[1]: haproxy.service: Service hold-off time over, scheduling restart.
Jun 07 10:50:01 ubuntu1604 systemd[1]: Stopped HAProxy Load Balancer.
Jun 07 10:50:01 ubuntu1604 systemd[1]: haproxy.service: Start request repeated too quickly.
Jun 07 10:50:01 ubuntu1604 systemd[1]: Failed to start HAProxy Load Balancer.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
It is needed to check haproxy health after all haproxy tasks were performed
playbook should fail if haproxy isn't started successfully