=== meetingology` is now known as meetingology
[08:19] <scahartner> hi all. thanks for being online. would you guys be able to help me with a cloud-init question ?
[08:27] <scahartner> I am looking for some pointers to use the nocloud datasource on a bare metal system running ubuntu 20.04 LTS. I tried updating the grub config adding the ds=nocloud-net;seedfrom=http://192.168.0.172/ubuntu/config/. but this didn't work
[08:42] <MAbeeTT> hello scahartner I am not expert in cloud-init but answering this basic questions might help you. Do you see the string ds=nocloud-net; in cat /proc/cmdline ? does your server web in 192.168.0.172 get a request?
[10:05] <scahartner> sorry, had some network issues.
[10:23] <MAbeeTT> scahartner: so you solved the issue?
[10:30] <scahartner> Nope. not yet
[10:30] <scahartner> The datasource still reports as None, and no requests are being made to the webserver
[14:06] <Odd_Bloke> scahartner: Could you pastebin /var/log/cloud-init.log, please?
[14:18] <Odd_Bloke> We have another potential cloud-init regression: https://bugs.launchpad.net/bugs/1911680
[14:18] <ubot5> Ubuntu bug 1911680 in cloud-init "Wrong access permissions of authorized keys file and parent directory when using absolute AuthorizedKeysFile" [Undecided,New]
[14:18] <Odd_Bloke> I'm investigating now.
[16:40] <scahartner> any thoughts on how to use nocloud datasource for bare metal on ubuntu 20.04 with grub
[16:42] <scahartner> https://pastebin.ubuntu.com/p/zDbypXpkMt/
[16:43] <scahartner> I am using PXE boot to do the minimal ubuntu install of 20.04 LTS. I am hoping that after the initial installation, that I can use cloud-init / nocloud to apply additional configuration for security etc.
[16:44] <scahartner> the PXE boot with auto-install is working well, but the first boot after the install never makes any calls. I tried updating grub with  ds=nocloud-net;seedfrom=http://192.168.0.172/ubuntu/config/ but it never calls the server
[17:14] <rharper> scahartner:  subiquity uses cloud-init on first boot to configure the system;  so I think you want to extend the cloud-config that's used to include the other things you'd like to do;  see this comment around some customization using cloud-init and autoinstall;  https://bugs.launchpad.net/subiquity/+bug/1907107/comments/19
[17:14] <ubot5> Ubuntu bug 1907107 in cloud-init (Ubuntu) "cloud-init runs too late at first startup after ubuntu autoinstall" [Undecided,Incomplete]
[23:07] <ajmyyra> I'm currently converting datasource network config to version 2, and have run into some problems with stateless DHCPv6. as v2 is missing subnet type, it's only possible to toggle 'dhcp' and 'accept_ra' settings. tests for this under unittests/test_net.py are a bit confusing as same Netplan is expected to produce two different ENIs: https://pastebin.com/Y1uD257c
[23:08] <ajmyyra> any suggestions how could I achieve the stateless v6 config matching the lower expected ENI?
[23:09] <ajmyyra> my confusion is probably due to the fact that network config v2 seems to be valid netplan configuration, but I might be mistaken with this
[23:11] <ajmyyra> netplan has this expired issue on it and it seems that just setting "dhcpv6: true" and "accept_ra: true" would solve it, but doesn't it still produce nonfunctional ENI when converted?