Comment 10 for bug 1988401

reviewing with cloud-init team and lxd team, it appears this has been a latent bug in the 22.04+ LXD containers as well. The issue being a Host LXD 4.0 and any container relying on the LXD cloud-init datasource, along with the specific GoLang symbols (%s, though other special symbols may also be affected). original bug report against LXD:

https://github.com/lxc/lxd/issues/10231

This changes was not backported to LXD 4.0 branch, which is the LTS branch for Focal and Bionic. This means on Ubuntu Focal (20.04) and Bionic (18.04) hosts running a Jammy (22.04) guest or forward can still hit this specific bug

However, CPC released the change to 22.04 guests 7 months ago. The original bug in LXD shows that it surfaced in LXD 5.0 and was fixed there. This means 22.04 Host + 22.04 Guest is fine.

For 22.04 guests on hosts running LXD < 5, we want to ensure this bug is surfaced when it comes up so that users providing custom metadata see the issue.