community.general.dnf_versionlock module – Locks package versions in dnf based systems
Note
This module is part of the community.general collection (version 10.7.5).
You might already have this collection installed if you are using the ansible package.
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install community.general.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: community.general.dnf_versionlock.
New in community.general 4.0.0
Synopsis
- Locks package versions using the - versionlockplugin in- dnfbased systems. This plugin takes a set of name and versions for packages and excludes all other versions of those packages. This allows you to for example protect packages from being updated by newer versions. The state of the plugin that reflects locking of packages is the- locklist.
Requirements
The below requirements are needed on the host that executes this module.
- dnf 
- dnf-plugin-versionlock 
Parameters
| Parameter | Comments | 
|---|---|
| Package name spec to add or exclude to or delete from the  This parameter is mutually exclusive with  Default:  | |
| Do not resolve package name specs to NEVRAs to find specific version to lock to. Instead the package name specs are used as they are. This enables locking to not yet available versions of the package. Choices: 
 | |
| Whether to add ( 
 
 
 
 Choices: 
 | 
Attributes
| Attribute | Support | Description | 
|---|---|---|
| Support: partial The logics of the  Sometimes the module could predict changes in  | Can run in  | |
| Support: none | Will return details on what has changed (or possibly needs changing in  | 
Notes
Note
- In an ideal world, the - versionlockplugin would have a dry-run option to know for sure what is going to happen. So far we have to work with a best guess as close as possible to the behaviour inferred from its code.
- For most of cases where you want to lock and unlock specific versions of a package, this works fairly well. 
- Does not work with - dnf5.
Examples
- name: Prevent installed nginx from being updated
  community.general.dnf_versionlock:
    name: nginx
    state: present
- name: Prevent multiple packages from being updated
  community.general.dnf_versionlock:
    name:
      - nginx
      - haproxy
    state: present
- name: Remove lock from nginx to be updated again
  community.general.dnf_versionlock:
    name: nginx
    state: absent
- name: Exclude bind 32:9.11 from installs or updates
  community.general.dnf_versionlock:
    name: bind-32:9.11*
    state: excluded
- name: Keep bash package in major version 4
  community.general.dnf_versionlock:
    name: bash-0:4.*
    raw: true
    state: present
- name: Delete all entries in the locklist of versionlock
  community.general.dnf_versionlock:
    state: clean
Return Values
Common return values are documented here, the following are the fields unique to this module:
| Key | Description | 
|---|---|
| Locklist after module execution. Returned: success and (not check mode or state is clean) Sample:  | |
| Locklist before module execution. Returned: success Sample:  | |
| Package name specs meant to be added by versionlock. Returned: success Sample:  | |
| Package name specs meant to be deleted by versionlock. Returned: success Sample:  | 
