In preparation for the release of 2.10, many plugins and modules have migrated to Collections on Ansible Galaxy. For the current development status of Collections and FAQ see Ansible Collections Community Guide. We expect the 2.10 Porting Guide to change frequently up to the 2.10 release. Follow the conversations about collections on our various Communicating channels for the latest information on the status of the
This section discusses the behavioral changes between Ansible 2.9 and Ansible-base 2.10.
It is intended to assist in updating your playbooks, plugins and other parts of your Ansible infrastructure so they will work with this version of Ansible-base.
We suggest you read this page along with the Ansible-base Changelog for 2.10 to understand what updates you may need to make.
Ansible-base is mainly of interest for developers and users who only want to use a small, controlled subset of the available collections. Regular users should install ansible.
The complete list of porting guides can be found at porting guides.
Fixed a bug on boolean keywords that made random strings return ‘False’, now they should return an error if they are not a proper boolean Example:
diff: yes-was returning
A new fact,
ansible_processor_nprocreflects the number of vcpus available to processes (falls back to the number of vcpus available to the scheduler).
ansible-galaxy logincommand has been removed, as the underlying API it used for GitHub auth is being shut down. Publishing roles or collections to Galaxy via
ansible-galaxynow requires that a Galaxy API token be passed to the CLI via a token file (default location
~/.ansible/galaxy_token) or (insecurely) via the
Windows Server 2008 and 2008 R2 will no longer be supported or tested in the next Ansible release, see Are Server 2008, 2008 R2 and Windows 7 supported?.
Links on this page may not point to the most recent versions of modules. We will update them when we can.
Version 2.10.0 of ansible-base changed the default mode of file-based tasks to
0o600 & ~umaskwhen the user did not specify a
modeparameter on file-based tasks. This was in response to a CVE report which we have reconsidered. As a result, the mode change has been reverted in 2.10.1, and mode will now default to
0o666 & ~umaskas in previous versions of Ansible.
If you changed any tasks to specify less restrictive permissions while using 2.10.0, those changes will be unnecessary (but will do no harm) in 2.10.1.
To avoid the issue raised in CVE-2020-1736, specify a
modeparameter in all file-based tasks that accept it.
yum- As of version 2.10.1, the
yumaction when it uses
dnf) now correctly validates GPG signatures of packages (CVE-2020-14365). If you see an error such as
Failed to validate GPG signature for [package name], please ensure that you have imported the correct GPG key for the DNF repository and/or package you are using. One way to do this is with the
rpm_keymodule. Although we discourage it, in some cases it may be necessary to disable the GPG check. This can be done by explicitly adding
disable_gpg_check: yesin your
Ansible modules created with
add_file_common_args=Trueadded a number of undocumented arguments which were mostly there to ease implementing certain action plugins. The undocumented arguments
directory_modeare now no longer added. Modules relying on these options to be added need to specify them by themselves.
Ansible no longer looks for Python modules in the current working directory (typically the
remote_user’s home directory) when an Ansible module is run. This is to fix becoming an unprivileged user on OpenBSD and to mitigate any attack vector if the current working directory is writable by a malicious user. Install any Python modules needed to run the Ansible modules on the managed node in a system-wide location or in another directory which is in the
$PYTHONPATHand readable by the
Prior to Ansible
2.10lookup plugin names passed in as an argument to the
lookup()function were treated as case-insensitive as opposed to lookups invoked via
2.10brings consistency to
with_to be both case-sensitive.
Cache plugins in collections can be used to cache data from inventory plugins. Previously, cache plugins in collections could only be used for fact caching.
Some undocumented arguments from
FILE_COMMON_ARGUMENTShave been removed; plugins using these, in particular action plugins, need to be adjusted. The undocumented arguments which were removed are
Action plugins that call modules should pass explicit, fully-qualified module names to
_execute_module()whenever possible (eg,
file). This ensures that the task’s collection search order is not consulted to resolve the module. Otherwise, a module from a collection earlier in the search path could be used when not intended.