The zuul-jobs stage-output role is useful in preparing logs for permanent storage. Previously the default behavior of this role was to compress logs that it collects to reduce storage space requirements (via a default true value for stage_compress_logs). Unfortunately, we've found that depending on the permanent storage system this may be undesireable. Specifically when storing logs in object storage services we can upload and store a compressed version of the file while still logically referring to it via its uncompressed name. Then the object storage service will convert it to the uncompressed version when retrieved. This is problematic if you want a compressed file to be worked with in its compressed form, like a .tar.gz tarball. In order to disambiguate between files that are intentionally compressed (like tarballs) and those that are compressed for storage efficiency reasons we are changing the default of stage_compress_logs to false and letting the upload roles determine how to compress things. In the case of upload-logs-swift already compressed files will be left alone and not treated special by the storage service. Any uncompressed files will be compressed on upload with hints to get the original back when retrieved. This should create a good balance of storage efficiency while still being able to work with intentionally compressed files without unexpected decompression from storage services. If you would like to keep the old stage-output behavior you can set stage_compress_logs to true in your site variables or base jobs. More details can be found in the change that updates stage-output, https://review.opendev.org/#/c/701282/. Clark