Ansible v2.16.20 - Logging, filter, and fact gathering fixes


Ansible ansible-core v2.16.20, published on November 2, 2026, fixes Windows connection logging that could expose raw task output despite no_log: true. This is a regular release, not a prerelease. For operators provisioning data processing hosts, it also changes filter results and fixes parallel fact gathering failures.

The release notes and distribution downloads are on the GitHub release page. The linked versioned changelog supplies the change details; this post covers its v2.16.20 section.

The psrp and winrm connection plugins no longer log raw stdout and stderr at verbosity 5 when a task sets no_log: true. The changelog classifies both corrections as security fixes. The trigger is specific: a task requests output suppression, but the connection logs still expose its raw output at that verbosity.

This matters when debugging provisioning tasks that handle credentials or return sensitive configuration. A verbose diagnostic run should preserve the task’s request to suppress output. Teams using either Windows connection plugin have a concrete reason to review this patch, especially where automation logs feed a shared logging system.

Keep the scope precise when recording the upgrade. These entries cover raw stdout and stderr at verbosity 5 for those two plugins. They do not describe a general change to logging across every connection plugin.

The bool filter now always produces a boolean. Passing None returns False; previously, it returned None. A playbook that distinguishes a missing value from an explicit false value can therefore observe a changed result. That distinction deserves attention in conditions controlling whether a provisioning or data preparation task runs.

There is also a deprecation attached to this filter. Coercion of unrecognized inputs, including None, is deprecated. Getting False today does not make missing input an accepted value for future use. Review the inputs passed to bool, and consider the truthy and falsy tests where their semantics fit.

The from_yaml_all filter now returns an empty list for both None and an empty string. Previously, these inputs returned None in Jinja native mode and an empty list in classic mode. For automation that reads YAML documents before building a processing environment, the result now has the same type in both modes. Check downstream expressions that explicitly test for None; those branches will see an empty list instead.

Two changes address parallel fact gathering. One fixes a hang caused by corrupt async job files. If provisioning stalled during fact collection, that failure mode belongs in the upgrade review. The changelog names the corrupt files as the cause but does not specify how they became corrupt.

The other change concerns timeout handling in the async wrapper. Previously, it slept for five seconds twice before checking whether the job had time remaining. The wrapper now considers the timeout when deciding whether to kill the process running the module.

These are useful reliability corrections for automation that must complete before processing jobs can start. The timeout entry does not promise a fixed reduction in runtime. Its stated change is to the decision about terminating the module process.

Review warnings from conditional expressions as part of testing this version. Literal None and empty string expressions in when or assert’s that currently evaluate as true and emit a deprecation warning. The notes schedule removal of that behavior for Ansible Core 2.23. Remove those expressions or make them return a strict boolean.

Templating also gains a warning for unknown types in finalized results. It appears once per unknown type per process and leaves the result unchanged. Use the warning to locate affected templates; it does not mean this release has rejected their output.