cloud-init uses gnupg

This bug was originally filed in Launchpad as [LP: #1949602](https://bugs.launchpad.net/cloud-init/+bug/1949602)

Launchpad details

affected_projects = []

assignee = None

assignee_name = None

date_closed = None

date_created = 2021-11-03T15:11:51.940060+00:00

date_fix_committed = None

date_fix_released = None

id = 1949602

importance = medium

is_complete = False

lp_url = https://bugs.launchpad.net/cloud-init/+bug/1949602

milestone = None

owner = juliank

owner_name = Julian Andres Klode

private = False

status = triaged

submitter = juliank

submitter_name = Julian Andres Klode

tags = []

duplicates = []

_Launchpad user **Julian Andres Klode(juliank)** wrote on 2021-11-03T15:11:51.940060+00:00_

The fix for bug 1836336 made cloud-init use gpg directly, which is odd, given that the reason for getting rid of apt-key is that gpg might not be around in systems (and honestly, shouldn't be).

Start by tracing where cloud-init invokes gpg, including the behavior introduced by the fix for bug 1836336. Determine how key handling should work when gpg is unavailable, then verify that the resulting cloud-init behavior no longer depends on direct gpg use while preserving the affected package-management workflow.

Written by the indexing model from the issue text.