[09:44] <hydro-b> Hi there. I'm trying to install ubuntu with autoinstall in a IPv6 only environment. This used to work fine with d-i / preseed, but I'm trying to convert it to the newish autoinstall way of life. There is a ISC dhcpv6 server active (configured simlarly to https://wiki.ubuntu.com/UEFI/SecureBoot/PXE-IPv6). IPv6 RAs also working. I made a first attempt on a user-data cloud-init config
[09:44] <hydro-b> (https://pastebin.ubuntu.com/p/Vvx7HxGKgw/). I can see in the webserver logs that the file (and meta-data / vendor-data, both empty files) are downloaded. However, the autoinstall does not start. The installer stops with a prompt: "choose type of install". Note, I have added the kernel cmdline option "autoinstall": https://pastebin.ubuntu.com/p/TnJC4CvYf5/.
[09:46] <hydro-b> So I'm running into a few issues actually. 1) I would like to avoid "ip=dhcp" ... or hint that the live-server skips trying dhcpv4 ... and only uses dhcp6. However, dhcp6 i not recognized (ISC dhcp client will give an error about this)
[09:46] <hydro-b> currently it takes 5 minutes for the first round of DHCP timeouts
[09:48] <hydro-b> Then an attempt is made to actually load the iso ... which works fine (over IPv6) ... then another round of DHCPv4 timeouts ... and after that the installer is started and cloud-init config files are downloaded
[09:50] <hydro-b> So, one question I have, where can I check if the cloud-init config file that is downloaded is actually parsed / used?
[09:51] <hydro-b> I've learned that after a manual install, a "/var/log/installer/autoinstall-user-data" should be created. Hence I thought I would try a manual install. But then I run into some other issues ...
[09:57] <hydro-b> The first is network configuration. The installer lets me configure dhcpv6 (and disable dhcpv4), which is great. However, although it succesfully managed to get an IPv6 address, has working IPv6 internet connectivity, resolving does not work. So in the next step (Configure ubuntu archive mirror) it fails to resolve the mirrors. Sidenote: I found in the installer logs that a geoip check is tried, but
[09:57] <hydro-b> it is not working either, as geoip.ubuntu.com does not have a quad A record set. I know for sure the DHCPv6 server hands out a nameserver (it works fine with dhclient in an initramfs). So the systemd stub-resolver is not configured to try lookups via IPv6 (haven't checked the config, but that is what I suspect).
[09:57] <hydro-b> that's easy to configure by removing the symlink to the stub resolver and manually enter the nameserver entry in /etc/resolv.conf ... resolving works ... up to the next step
[09:57] <mwhudson> hydro-b: to check if the autoinstall / cloud-init config is found, looking in /var/lib/cloud-init.log would be a good start
[09:58] <hydro-b> mwhudson: ah, I will check right away
[09:58] <mwhudson> the name resolution stuff sounds like a bug, i don't have much experience in ipv6-only environments
[09:58] <hydro-b> mwhudson: I'm used to find IPv6 only bugs ;-)
[09:58] <mwhudson> hydro-b: we are going to try to make it more obvious when cloud-init has issues
[10:00] <hydro-b> that would be great. There has been a lot of advancements in this area (cloud-config, autoinstall, their interaction). It probably works awesome if you know all the moving parts work
[10:00] <hydro-b> /var/lib/cloud-init.log <- this file does not exist
[10:01] <hydro-b> I think I found it
[10:02] <mwhudson> sorry /var/log
[10:02] <hydro-b> /var/log/cloud-init.log does exist
[10:02] <mwhudson> it is late here :)
[10:02] <hydro-b> haha, appreciate your time
[10:05] <hydro-b> 023-10-19 09:24:29,167 - util.py[WARNING]: Failed loading yaml blob. Invalid format at line 34 column 16: "mapping values are not allowed here
[10:05] <hydro-b>   in "<unicode string>", line 34, column 16:
[10:05] <hydro-b>       late-commands:
[10:06] <hydro-b> I used the "autoinstall-generator" to convert from preseed ... but apparently it's inserting statements that are not allowed
[10:06] <hydro-b> I'll try to strip it down to bare minimum for now
[10:08] <hydro-b> and try again
[10:08] <hydro-b> And I'll file a bug for the nameserver resolving issue
[10:12] <mwhudson> hydro-b: yeah that kind of error is what we need to expose in the ui
[10:35] <hydro-b> mwhudson: is there a way with the intaller to configure UEFI partitions (vfat)? I seem to only be able to choose ext4, btrs, xfs, swap
[11:01] <bdrung> @pilot in
[13:17] <ahasenack> coreycb: hi, I'm about to release cinder into lunar, and was wondering about your test results in https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/2037319/comments/4
[13:17] -ubottu:#ubuntu-devel- Launchpad bug 2037319 in cinder (Ubuntu Lunar) "[SRU] antelope stable releases" [High, Fix Committed]
[13:17] <ahasenack> you say you used 2:22.1.1-0ubuntu1~cloud0, but that's from the cloud archive I suppose, not lunar-proposed
[13:18] <ahasenack> coreycb: could you please confirm in the bug if lunar-proposed is verified, or just cloud-archive?
[13:20] <coreycb> ahasenack: thanks for taking a look. it should have results for lunar above that (including package version from lunar-proposed). let me know if it needs clarification.
[13:20] <ahasenack> coreycb: ah, you are right, I skimmed to the end of the comment and only saw the UCA version
[13:20] <ahasenack> but in the middle of the comment you also mentioned the lunar version
[13:20] <ahasenack> my bad
[13:20] <ahasenack> all good
[16:35] <bdrung> @pilot out
[17:14] <amikhalitsyn> Dear friends, I need advice regarding fixing the LXC package in Ubuntu Jammy. I've filled a bug https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873 but as far as I understand I need someone from the SRU team to make that. And nobody in my team (LXD) do not have enough permissions to update packages.
[17:14] -ubottu:#ubuntu-devel- Launchpad bug 2039873 in lxc (Ubuntu) "liblxc-dev was built with LXC_DEVEL=1 in Ubuntu Jammy/Kinetic" [Undecided, New]
[17:57] <kanashiro> @pilot in
[21:59] <kanashiro> @pilot out