become sudo not working for apt module

Archives Ansible Project
,
1

Hi

I have a number of ubuntu servers that I want to update using ansible via AWX. my current test playbook :

2

Have you tried a ps on the host you are trying to upgrade to see if an apt command is already running? I’ve run into it before where an auto update is running, so it has the lock file already in place.

–john

3

Hi

I have a number of ubuntu servers that I want to update using ansible via AWX. my current test playbook :

---
- hosts: all
tasks:
- name: Test Connection
ansible.builtin.ping:

\- name: Update Cache
  become: true
  apt:
    update\_cache: true

is not work as expected on the ubuntu servers.
The servers that have the root user configured are fine. But the Ubuntu servers where the root user doesn't have a password set are failing with the following error:

"Failed to lock apt for exclusive operation: Failed to lock directory /var/lib/apt/lists/: E:Could not open lock file /var/lib/apt/lists/lock - open (13: Permission denied)"

In AWX I have configured privilege escalation to use sudo but this doesnt help.

I have tried moving the become: yes statement but this did help.

Doe the apt module support the sudo ?

What have I missed ?

Thank you

Greg

Hello Greg,

you miss "become: true" in your playbook-

Regards
   Racke

4

FYI, become is independent of modules, it wraps module execution so
modules do not need to enable/support it. Connection plugins on the
other hand can affect how become works, in the case of local, windows
and networking appliances.