AIO after reboot haproxy role fails

Bug #1819790 reported by DimGR
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
New
Undecided
Unassigned

Bug Description

hello
ubuntu bionic and tag 18.1.4
following the official AIO how to , a dev aio builds fine with no errors
Once I reboot the server and log back in i notice that the lxc service is not running and the containers have no ip address. I start this service via systemctl and they get an ip. So far so good.
Horizon fails to load so i guess its a matter of rebuilding the AIO per the official documents.
The rebuild starts and fails at this point with this error:

RUNNING HANDLER [haproxy_endpoints : Set haproxy service state] ****************************************************************************************************************************************************************************************************************
failed: [aio1_galera_container-0a49954d -> 172.29.236.100] (item=aio1) => {"changed": false, "item": "aio1", "module_stderr": "Shared connection to 172.29.236.100 closed.\r\n", "module_stdout": "Traceback (most recent call last):\r\n File \"/tmp/ansible_ez7fR0/ansible_module_haproxy.py\", line 458, in <module>\r\n main()\r\n File \"/tmp/ansible_ez7fR0/ansible_module_haproxy.py\", line 454, in main\r\n ansible_haproxy.act()\r\n File \"/tmp/ansible_ez7fR0/ansible_module_haproxy.py\", line 403, in act\r\n state_before = self.get_state_for(self.backend, self.host)\r\n File \"/tmp/ansible_ez7fR0/ansible_module_haproxy.py\", line 334, in get_state_for\r\n data = self.execute('show stat', 200, False).lstrip('# ')\r\n File \"/tmp/ansible_ez7fR0/ansible_module_haproxy.py\", line 254, 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": 1}

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.