This bug was fixed in the package cloud-init - 23.1.1-0ubuntu2
---------------
cloud-init (23.1.1-0ubuntu2) lunar; urgency=medium
* d/apport-general-hook.py: Add general apport hook to append cloud type,
image and instance size information to bug reports (LP: #1724623)
* d/cloud-init.postinst: MAAS prefer yaml.safe_load over yaml.load
(LP: #2009746)
* d/cloud-init.preinst: Oracle to remove vestigial /etc/cloud.cloud.cfg.d/
99-disable-network-config.cfg because system config is now honored before
datasource config (LP: #1956788)
* Upstream snapshot based on upstream/main at 85b2fbc2.
- Bugs fixed in this snapshot: (LP: #1956788)
-- Chad Smith <chad.sm...@canonical.com> Tue, 21 Mar 2023 14:43:55
-0600
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1724623
Title:
Update ubuntu cloud info
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in cloud-init package in Ubuntu:
Fix Released
Bug description:
add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul.
Issues:
- Using the presence of cloud-init to flag an image as a cloud image is
incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images)
- Using the presence of EC2 metadata source is incorrect as many non-EC2
clouds provide EC2 metadata. Thus we have bugs like bug #1722946 that are
tagged as an 'ec2-images' bug which are clearly on openstack
- Marking all bugs that have cloud-init but no EC2 metadata source as an
'uec-images' bug uses a name that no longer has meaning.
Solution:
- If cloud-init is present, check for /etc/cloud/build.info to indicate an
Ubuntu cloud images, tag as 'cloud-images'. Pull the build_name and serial
from that file into the bug comments.
- If cloud-init is present, check for the presence of
/run/cloud-init/cloud.cfg. Parse this yaml to determine the datasource type.
Add the datasource used to the bug comment.
I have filed bug #1724626 to ask cloud-init development to surface
more information from ds-identify to help ID the cloud so that we can
better tag/annotate the bug. There may also be some info we can get
to indicate the image ID on more clouds than just AWS. At a minimum I
would like to see dsidentify make the EC2 platform it found available
for consumers in cloud.cfg. This would allow us to identify AWS EC2
from look-alike datasources so that we can tag a bug as ec2-images for
bug really on AWS and add EC2 specific fields to the
description/attachments.
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1724623/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
