ansible.builtin.apt_key module doesn't work with binary gpg keys in ansible v4.0.0

[dmitryax]

Summary

Using ansible.builtin.apt_key to import a binary gpg key started failing with release of ansible 4.0.0. It works well on other versions of ansible 2.9+.

Issue Type

Bug Report

Component Name

apt_key

Ansible Version

ansible [core 2.11.0]
  config file = None
  configured module search path = ['/Users/danoshin/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.9/site-packages/ansible
  ansible collection location = /Users/danoshin/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.9.5 (default, May  4 2021, 03:33:11) [Clang 12.0.0 (clang-1200.0.32.29)]
  jinja version = 2.11.3
  libyaml = True

Configuration

(empty)

OS / Environment

control host: MacOS 10.15.7
remove host: Ubuntu 20.04.2 LTS

Steps to Reproduce

Try to add any binary gpg key:

    - name: Add binary key
      apt_key: 
        url: https://packages.cloud.google.com/apt/doc/apt-key.gpg

Expected Results

The gpg key added to the keyring

Actual Results

TASK [Add binary key] **********************************************************************************************************************************************************************************************************************************************************
fatal: [ubuntu]: FAILED! => {"changed": false, "msg": "Unable to extract key from '-'", "stderr": "gpg: directory '/root/.gnupg' created\ngpg: keybox '/root/.gnupg/pubring.kbx' created\ngpg: WARNING: no command supplied.  Trying to guess what you mean ...\ngpg: /root/.gnupg/trustdb.gpg: trustdb created\ngpg: [don't know]: invalid packet (ctb=0a)\n", "stderr_lines": ["gpg: directory '/root/.gnupg' created", "gpg: keybox '/root/.gnupg/pubring.kbx' created", "gpg: WARNING: no command supplied.  Trying to guess what you mean ...", "gpg: /root/.gnupg/trustdb.gpg: trustdb created", "gpg: [don't know]: invalid packet (ctb=0a)"], "stdout": "pub:-:2048:1:FEEA9169307EA071:1614614617:1677728521::-:\nuid:::::::::Rapture Automatic Signing Key (cloud-rapture-signing-key-2021-03-01-08_01_09.pub):\nsub:-:2048:1:AA42F36EE8BEEE0E:1614614617::::\npub:-:2048:1:8B57C5C2836F4BEB:1607040606:1670154510::-:\nuid:::::::::gLinux Rapture Automatic Signing Key (//depot/google3/production/borg/cloud-rapture/keys/cloud-rapture-pubkeys/cloud-rapture-signing-key-2020-12-03-16_08_05.pub) <glinux-team@google.com>:\nsub:-:2048:1:48419E688DD52AC0:1607040606::::\n", "stdout_lines": ["pub:-:2048:1:FEEA9169307EA071:1614614617:1677728521::-:", "uid:::::::::Rapture Automatic Signing Key (cloud-rapture-signing-key-2021-03-01-08_01_09.pub):", "sub:-:2048:1:AA42F36EE8BEEE0E:1614614617::::", "pub:-:2048:1:8B57C5C2836F4BEB:1607040606:1670154510::-:", "uid:::::::::gLinux Rapture Automatic Signing Key (//depot/google3/production/borg/cloud-rapture/keys/cloud-rapture-pubkeys/cloud-rapture-signing-key-2020-12-03-16_08_05.pub) <glinux-team@google.com>:", "sub:-:2048:1:48419E688DD52AC0:1607040606::::"]}

Code of Conduct

• I agree to follow the Ansible Code of Conduct

[ansibot]

Files identified in the description:

• lib/ansible/modules/apt_key.py

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help

[sivel]

This has been resolved in #74474 and will be included in the upcoming ansible-core 2.11.1 release on May 24.

If you have further questions please stop by IRC or the mailing list:

• IRC: #ansible on irc.freenode.net
• mailing list: https://groups.google.com/forum/#!forum/ansible-project

[dmitryax]

Thanks! Confirmed using v2.11.1rc1 release