I'm experiencing the same bug on ussuri, 5 node cluster where the second controller node is stuck with galera being restarted and ansible stuck on "mariadb : Wait for MariaDB service port liveness" task.
I see also in a source code this commente "# NOTE(yoctozepto): We have to loop this to avoid breaking on connection resets" on-top of the handler task for port liveness.
Can somebody confirm that this is an existing bug and still not fixed and on recommended solution?
Thank you
2020-10-19 07:44:08,242 p=601358 u=lineng n=ansible | RUNNING HANDLER [mariadb : Wait for MariaDB service port liveness] *************
2020-10-19 07:50:21,448 p=601358 u=lineng n=ansible | An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ConnectionResetError: [Errno 104] Connection reset by peer
2020-10-19 07:50:21,449 p=601358 u=lineng n=ansible | fatal: [osce5]: FAILED! => {"attempts": 10, "changed": false, "module_stderr": "Shared connection to 192.168.1.8 closed.\r\n", "module_stdout": "Traceback (most recent call last):\r\n File \"/home/lineng/.ansible/tmp/ansible-tmp-1603082990.52845-603995-148496658340252/AnsiballZ_wait_for.py\", line 102, in <module>\r\n _ansiballz_main()\r\n File \"/home/lineng/.ansible/tmp/ansible-tmp-1603082990.52845-603995-148496658340252/AnsiballZ_wait_for.py\", line 94, in _ansiballz_main\r\n invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\r\n File \"/home/lineng/.ansible/tmp/ansible-tmp-1603082990.52845-603995-148496658340252/AnsiballZ_wait_for.py\", line 40, in invoke_module\r\n runpy.run_module(mod_name='ansible.modules.utilities.logic.wait_for', init_globals=None, run_name='__main__', alter_sys=True)\r\n File \"/usr/lib64/python3.6/runpy.py\", line 205, in run_module\r\n return _run_module_code(code, init_globals, run_name, mod_spec)\r\n File \"/usr/lib64/python3.6/runpy.py\", line 96, in _run_module_code\r\n mod_name, mod_spec, pkg_name, script_name)\r\n File \"/usr/lib64/python3.6/runpy.py\", line 85, in _run_code\r\n exec(code, run_globals)\r\n File \"/tmp/ansible_wait_for_payload_akcbsjk8/ansible_wait_for_payload.zip/ansible/modules/utilities/logic/wait_for.py\", line 687, in <module>\r\n File \"/tmp/ansible_wait_for_payload_akcbsjk8/ansible_wait_for_payload.zip/ansible/modules/utilities/logic/wait_for.py\", line 615, in main\r\nConnectionResetError: [Errno 104] Connection reset by peer\r\n", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}
Hi all.
I'm experiencing the same bug on ussuri, 5 node cluster where the second controller node is stuck with galera being restarted and ansible stuck on "mariadb : Wait for MariaDB service port liveness" task.
I see also in a source code this commente "# NOTE(yoctozepto): We have to loop this to avoid breaking on connection resets" on-top of the handler task for port liveness.
Can somebody confirm that this is an existing bug and still not fixed and on recommended solution?
Thank you
2020-10-19 07:44:08,242 p=601358 u=lineng n=ansible | RUNNING HANDLER [mariadb : Wait for MariaDB service port liveness] ************* Error: [Errno 104] Connection reset by peer lineng/ .ansible/ tmp/ansible- tmp-1603082990. 52845-603995- 148496658340252 /AnsiballZ_ wait_for. py\", line 102, in <module>\r\n _ansiballz_ main()\ r\n File \"/home/ lineng/ .ansible/ tmp/ansible- tmp-1603082990. 52845-603995- 148496658340252 /AnsiballZ_ wait_for. py\", line 94, in _ansiballz_main\r\n invoke_ module( zipped_ mod, temp_path, ANSIBALLZ_ PARAMS) \r\n File \"/home/ lineng/ .ansible/ tmp/ansible- tmp-1603082990. 52845-603995- 148496658340252 /AnsiballZ_ wait_for. py\", line 40, in invoke_module\r\n runpy.run_ module( mod_name= 'ansible. modules. utilities. logic.wait_ for', init_globals=None, run_name= '__main_ _', alter_sys=True)\r\n File \"/usr/ lib64/python3. 6/runpy. py\", line 205, in run_module\r\n return _run_module_ code(code, init_globals, run_name, mod_spec)\r\n File \"/usr/ lib64/python3. 6/runpy. py\", line 96, in _run_module_ code\r\ n mod_name, mod_spec, pkg_name, script_name)\r\n File \"/usr/ lib64/python3. 6/runpy. py\", line 85, in _run_code\r\n exec(code, run_globals)\r\n File \"/tmp/ ansible_ wait_for_ payload_ akcbsjk8/ ansible_ wait_for_ payload. zip/ansible/ modules/ utilities/ logic/wait_ for.py\ ", line 687, in <module>\r\n File \"/tmp/ ansible_ wait_for_ payload_ akcbsjk8/ ansible_ wait_for_ payload. zip/ansible/ modules/ utilities/ logic/wait_ for.py\ ", line 615, in main\r\ nConnectionRese tError: [Errno 104] Connection reset by peer\r\n", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}
2020-10-19 07:50:21,448 p=601358 u=lineng n=ansible | An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ConnectionReset
2020-10-19 07:50:21,449 p=601358 u=lineng n=ansible | fatal: [osce5]: FAILED! => {"attempts": 10, "changed": false, "module_stderr": "Shared connection to 192.168.1.8 closed.\r\n", "module_stdout": "Traceback (most recent call last):\r\n File \"/home/