Artem Goncharov 179a966655 dont wait infinitely for the connection to zuul_console server ... If security group or firewall on the target node silently drop connection to zuul_console daemon - do not wait infinitely and instead show a message. After spending days figuring out the reason for zuul_console/stream not working properly and figuring out that the default group of the node does not allow 19885 connection from zuul-master (in default and zuul security group) it became clear, that some extra information is required back to user. I am open for making it timeout configurable, but 5 sec should be enough initially. Change-Id: I4e395b650e83a78d66aa362a420ef0d836c80d35		2018-05-11 15:42:08 +02:00
..
action	Allow some plugins to read from playbook dir	2018-04-05 10:40:51 -07:00
callback	dont wait infinitely for the connection to zuul_console server	2018-05-11 15:42:08 +02:00
filter	Be explicit about legacy var additions/omissions	2017-10-17 18:28:43 +00:00
library	Fix broken fail_json in zuul_console	2018-02-12 09:02:46 +01:00
lookup	Allow some plugins to read from playbook dir	2018-04-05 10:40:51 -07:00
__init__.py	Ansible launcher: add zuul_runner module	2016-05-12 11:37:19 -07:00
logconfig.py	Use deepcopy when copying ansible logging config	2017-09-06 18:03:12 -07:00
paths.py	Check out more appropriate branches of role and playbook repos	2018-04-05 10:41:51 -07:00