> Which component is responsible for generating /etc/cloud/build.info? livecd-rootfs, during image creation time.
https://git.launchpad.net/livecd-rootfs/tree/live-build/auto/build#n452 it'll have at least 1 value, serial (in the case of an OCI container), normally 2: serial, build_name > From my perspective add_cloud_init_data and get_ec2_data should be shipped by cloud-init, because they access data generated by cloud-init. I'll leave the cloud-init team to comment, but I actually disagree. `/run/cloud-init/instance-data.json` is one of several user parseable files generated by cloud-init. the "native" cloud-init error reporting would be to, as smoser said (back in 2018) is to do `cloud-init collect- logs`. That produces a tar file so it can't directly be added to the `apport` report. I'm not against shipping the cloud-init logs along with any cloud image based issue being reported. I'd have to dig in a little to see how `apport` currently creates a bundle, and how easy it'd be to add the cloud-init bundle as well. But know that we'll be delivering a _lot_ more information in the apport bug report. -- 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 package in Ubuntu: New Status in cloud-init package in Ubuntu: New 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/ubuntu/+source/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
