summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorIan Wienand <iwienand@redhat.com>2022-08-31 14:50:19 +1000
committerIan Wienand <iwienand@redhat.com>2022-09-14 11:19:40 +1000
commitc54ccda1283cda500ec2e83be2b8769ce261fd7b (patch)
tree69977f65a6808cc6b1cf2cb824a38744adf5158c
parentc9fa64b4db2743e2c8716b2d41675e5c995ef34e (diff)
downloadzuul-c54ccda1283cda500ec2e83be2b8769ce261fd7b.tar.gz
zuul-stream: Add variable to disable writing streaming files
Upon further discussion we recently found another case of leaking console streaming files; if the zuul_console is not running on port 19885, or can not be reached, the streaming spool files will still be leaked. The prior work in I823156dc2bcae91bd6d9770bd1520aa55ad875b4 has the receiving side indicate to the zuul_console daemon that it should remove the spool file. If this doesn't happen, either because the daemon was never there, or it is firewalled off, the streaming spool files are left behind. This modifies the command action plugin to look for a variable "zuul_console_disable" which will indicate to the library running the shell/command task not to write out the spool file at all, as it will not be consumed. It is expected this would be set at a host level in inventory for nodes that you know can not or will not have access to zuul_console daemon. We already have a mechanism to disable this for commands running in a loop; we expand this with a new string type. The advantage of this is it leaves the library/command.py side basically untouched. Documentation is updated, and we cover this with a new test. Change-Id: I0273993c3ece4363098e4bf30bfc4308bb69a8b4
-rw-r--r--doc/source/howtos/nodepool_static.rst28
-rw-r--r--playbooks/zuul-stream/fixtures/test-stream.yaml8
-rw-r--r--playbooks/zuul-stream/functional.yaml9
-rw-r--r--zuul/ansible/base/action/command.py19
-rwxr-xr-xzuul/ansible/base/library/command.py5
5 files changed, 56 insertions, 13 deletions
diff --git a/doc/source/howtos/nodepool_static.rst b/doc/source/howtos/nodepool_static.rst
index c10672e7b..163497bcf 100644
--- a/doc/source/howtos/nodepool_static.rst
+++ b/doc/source/howtos/nodepool_static.rst
@@ -69,14 +69,30 @@ Log streaming
The log streaming service enables Zuul to show the live status of
long-running ``shell`` or ``command`` tasks. The server side is setup
by the ``zuul_console:`` task built-in to Zuul's Ansible installation.
-The executor requires the ability to communicate with the job nodes on
-port 19885 for this to work.
+The executor requires the ability to communicate with this server on
+the job nodes via port ``19885`` for this to work.
-The log streaming service may leave files on the static node in the
-format ``/tmp/console-<uuid>-<task_id>-<host>.log`` if jobs are
-interrupted. These may be safely removed after a short period of
-inactivity with a command such as
+The log streaming service spools command output via files on the job
+node in the format ``/tmp/console-<uuid>-<task_id>-<host>.log``. By
+default, it will clean these files up automatically.
+
+Occasionally, a streaming file may be left if a job is interrupted.
+These may be safely removed after a short period of inactivity with a
+command such as
.. code-block:: shell
find /tmp -maxdepth 1 -name 'console-*-*-<host>.log' -mtime +2 -delete
+
+If the executor is unable to reach port ``19885`` (for example due to
+firewall rules), or the ``zuul_console`` daemon can not be run for
+some other reason, the command to clean these spool files will not be
+processed and they may be left behind; on an ephemeral node this is
+not usually a problem, but on a static node these files will persist.
+
+In this situation, , Zuul can be instructed to not to create any spool
+files for ``shell`` and ``command`` tasks via setting
+``zuul_console_disable: True`` (usually via a global host variable in
+inventory). Live streaming of ``shell`` and ``command`` calls will of
+course be unavailable in this case, but no spool files will be
+created.
diff --git a/playbooks/zuul-stream/fixtures/test-stream.yaml b/playbooks/zuul-stream/fixtures/test-stream.yaml
index 0326ae54e..488f8cb2f 100644
--- a/playbooks/zuul-stream/fixtures/test-stream.yaml
+++ b/playbooks/zuul-stream/fixtures/test-stream.yaml
@@ -11,6 +11,14 @@
port: 19887
when: new_console | default(false)
+- name: Run command to show skipping works
+ vars:
+ zuul_console_disabled: true
+ hosts: node
+ tasks:
+ - name: Run quiet command
+ command: echo 'This command should not stream'
+
- name: Run some commands to show that logging works
hosts: node
tasks:
diff --git a/playbooks/zuul-stream/functional.yaml b/playbooks/zuul-stream/functional.yaml
index b8a44a87c..1d03e650b 100644
--- a/playbooks/zuul-stream/functional.yaml
+++ b/playbooks/zuul-stream/functional.yaml
@@ -74,7 +74,7 @@
mv job-output.txt job-output-success-19885.txt
mv job-output.json job-output-success-19885.json
- - name: Validate outputs
+ - name: Validate text outputs
include_tasks: validate.yaml
loop:
- { node: 'node1', filename: 'job-output-success-19887.txt' }
@@ -82,6 +82,13 @@
- { node: 'node1', filename: 'job-output-success-19885.txt' }
- { node: 'node2', filename: 'job-output-success-19885.txt' }
+ # This shows that zuul_console_disabled has activated and set the
+ # UUID to "skip"
+ - name: Validate json output
+ shell: |
+ egrep 'zuul_log_id": "skip"' job-output-success-19885.json
+ egrep 'zuul_log_id": "skip"' job-output-success-19887.json
+
# failure case
- name: Run ansible playbook that should fail
diff --git a/zuul/ansible/base/action/command.py b/zuul/ansible/base/action/command.py
index 3bb88d8e5..a969a8b2b 100644
--- a/zuul/ansible/base/action/command.py
+++ b/zuul/ansible/base/action/command.py
@@ -13,8 +13,10 @@
# You should have received a copy of the GNU General Public License
# along with this software. If not, see <http://www.gnu.org/licenses/>.
-
from zuul.ansible import paths
+
+from ansible.module_utils.parsing.convert_bool import boolean
+
command = paths._import_ansible_action_plugin("command")
@@ -25,10 +27,17 @@ class ActionModule(command.ActionModule):
if self._task.action in (
'command', 'shell',
'ansible.builtin.command', 'ansible.builtin.shell'):
- # This is a bit lame, but we do not log loops in the
- # zuul_stream.py callback. This allows us to not write
- # out command.py output to files that will never be read.
- if 'ansible_loop_var' in task_vars:
+ # Overloading the UUID is a bit lame, but it stops us
+ # having to modify the library command.py too much. Both
+ # of these below stop the creation of the files on disk
+ # for situations where they won't be read and cleaned-up.
+ skip = boolean(
+ self._templar.template(
+ "{{zuul_console_disabled|default(false)}}"))
+ if skip:
+ self._task.args['zuul_log_id'] = 'skip'
+ elif 'ansible_loop_var' in task_vars:
+ # we do not log loops in the zuul_stream.py callback.
self._task.args['zuul_log_id'] = 'in-loop-ignore'
else:
# Get a unique key for ZUUL_LOG_ID_MAP. ZUUL_LOG_ID_MAP
diff --git a/zuul/ansible/base/library/command.py b/zuul/ansible/base/library/command.py
index 3c22849ae..c52412edf 100755
--- a/zuul/ansible/base/library/command.py
+++ b/zuul/ansible/base/library/command.py
@@ -270,6 +270,8 @@ class Console(object):
# special-casing for any of this path.
if log_uuid == 'in-loop-ignore':
self.logfile_name = os.devnull
+ elif log_uuid == 'skip':
+ self.logfile_name = os.devnull
else:
self.logfile_name = LOG_STREAM_FILE.format(log_uuid=log_uuid)
@@ -494,7 +496,8 @@ def zuul_run_command(self, args, zuul_log_id, check_rc=False, close_fds=True, ex
try:
if self._debug:
- self.log('Executing: ' + self._clean_args(args))
+ self.log('Executing <%s>: %s',
+ zuul_log_id, self._clean_args(args))
# ZUUL: Replaced the execution loop with the zuul_runner run function