Hello Robert, or anyone else affected, Accepted cloud-init into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/23.2.1-0ubuntu0~22.04.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed-focal ** Tags added: verification-needed-focal -- 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 Status in cloud-init source package in Focal: Fix Committed Status in cloud-init source package in Jammy: Fix Committed Status in cloud-init source package in Kinetic: Fix Committed Status in apport source package in Lunar: New Status in cloud-init source package in Lunar: New Bug description: [ Impact ] Apport reported bug add invalid bug tags such as `uec-images` which no longer has meaning or `ec2-images` on openstack. Since cloud-init is installed in all these images and detects the correct datasource, leverage cloud-init's instance-data.json or cloud-id [ Test Plan ] 1. Launch LXD container for each series 2. upgrade to cloud-init from -proposed. 3. Execute apport-bug cloud-init and view report to assess that correct tags are present for LXD datasource. 4. replace /run/cloud-init/instance-data.json cloud-id content with examples from openstack, ec2, configdrive and assert appropriate tags match the platform details. verification scriptlet (attached): #!/bin/bash set -ex cat > setup_proposed.sh <<EOF #/bin/bash mirror=http://archive.ubuntu.com/ubuntu echo deb \$mirror \$(lsb_release -sc)-proposed main | tee /etc/apt/sources.list.d/proposed.list apt-get update -q apt-get install -qy cloud-init EOF cat > openstack.json <<EOF { "ds" : {}, "v1": { "cloud_id": "openstack", "cloud_name": "openstack", "machine": "CloudArchitecture", "platform": "openstack", "region": null, "subplatform": "metadata (http://169.254.169.254)" } } EOF cat > ec2.json << EOF { "ds": { "imageId": "ami-123", "instanceType": "m1.tiny", "region": "us-east-1" }, "v1": { "cloud_name": "aws", "distro": "ubuntu", "distro_release": "jammy", "distro_version": "22.04", "instance_id": "i-06b5687b4d7b8595d", "machine": "x86_64", "platform": "ec2", "python_version": "3.10.4", "region": "us-east-2", "variant": "ubuntu" } } EOF for release in focal jammy kinetic lunar; do VM=sru-$release lxc launch ubuntu-daily:$release $VM while ! lxc exec $VM -- cloud-init status --wait --long; do sleep 5 done echo --- 1. Generate current apport report, selecting Openstack as cloud. echo --- step through prompts and select 'K' to keep report lxc exec $VM -- apport-bug cloud-init APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport) lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.orig lxc exec $VM rm /tmp/$APPORT_FILE lxc file push setup_proposed.sh $VM/ lxc exec $VM -- bash /setup_proposed.sh | grep cloud-init lxc file push openstack.json $VM/run/cloud-init/instance-data.json echo --- 2. Generate -proposed apport report which sources openstack instance-data.json, selecting Openstack as cloud. lxc exec $VM -- apport-bug cloud-init APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport) lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.openstack-proposed lxc exec $VM rm /tmp/$APPORT_FILE echo --- 3. Generate -proposed apport report which sources ec2 instance-data, selecting Ec2 as cloud. lxc file push ec2.json $VM/run/cloud-init/instance-data.json lxc exec $VM -- apport-bug cloud-init APPORT_FILE=$(lxc exec $VM ls /tmp | grep apport) lxc file pull $VM/tmp/$APPORT_FILE apport-$VM.ec2-proposed lxc exec $VM rm /tmp/$APPORT_FILE # redact logs lines for easy diffs for file in `ls apport*`; do sed -i '1,/logs.tgz/!d' $file done echo --- 4. Inspect diff tags of orig to openstack-proposed report diff -urN apport-$VM.orig apport-$VM.openstack-proposed || true echo --- 5. Inspect diff tags of openstack-proposed to ec2-proposed report diff -urN apport-$VM.openstack-proposed apport-$VM.ec2-proposed || true done [ Where problems could occur ] apport-bug could traceback on poor logic preventing simple bug filing at apport CLI. It could omit tags if unable to process cloud-init/instance-data.json. nothing critical to daily performance, uptime or security [ Other Info ] [Original description] 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
