Comment 6 for bug 1724623

> 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.