[11:02] any feedback for https://github.com/canonical/cloud-init/pull/4234 ? [11:02] -ubottu:#cloud-init- Pull 4234 in canonical/cloud-init "tools/read-version: fix the tool so that it can handle version parsing errors" [Open] [13:23] blackboxsw: shouldn't the channel topic now mention Github for "bugs" rather than launchpad? === falcojr changed the topic of #cloud-init to: 23.2 Released 05/23 | https://github.com/canonical/cloud-init/issues/new/choose | PRs: https://git.io/JeVed | release schedule: https://discourse.ubuntu.com/t/2023-cloud-init-release-schedule/32244 === falcojr changed the topic of #cloud-init to: 23.2 Released 05/23 | File bug: https://github.com/canonical/cloud-init/issues/new/choose | PRs: https://git.io/JeVed | release schedule: https://discourse.ubuntu.com/t/2023-cloud-init-release-schedule/32244 [13:30] thanks minimal [13:30] Ani: I'll try to get to it today [13:33] Thanks! [14:58] As a follow up to the bug in cloud_init and userdata with Amazon Linux 2023, AWS confirmed they could reproduce it as well. Hopefully a fix comes soon from the project :) [15:46] JoBbZ: do you have a detailed procedure you've followed with terraform that could be added as a comment to the issue https://github.com/canonical/cloud-init/issues/4239? [15:47] -ubottu:#cloud-init- Issue 4239 in canonical/cloud-init "__init__.py[WARNING]: Unhandled non-multipart (text/x-not-multipart) userdata error" [Open] [15:48] I'm curious about the specific terraform aspect of setup/deployment when interacting with ec2 to have that documented somewhere. (As we should also improve docs related to terraform use-cases). [17:14] l