[15:48] <smoser> ahasenack or rbasak can we import sshuttle ?
[15:48] <smoser> 'git ubuntu' import
[15:48] <smoser> https://bugs.launchpad.net/ubuntu/+source/sshuttle/+bug/1873368
[15:49] <smoser> i dont knwo how people do anything without git ubuntu. if i am going to look at a package, the first step is checking for git-ubuntu and then bothering one of  you two (sorry for that).
[15:50] <ahasenack> smoser: sure
[15:50] <ahasenack> on it
[15:50] <ahasenack> rbasak: I'm pushing the config change
[15:52] <smoser> gracias
[15:56] <ahasenack> smoser: I'm monitoring it and will let you know
[15:57] <smoser> ahasenack: i'm not in any need of an update. thanks though.
[15:57] <ahasenack> it's dealing with a bunch of lancuage-pack imports atm
[15:58] <ahasenack> rbasak: something to think about: we could have a big queue, and a small queue, like dep8 tests
[15:58] <smoser> i just can't wait until all ubuntu packages are in it.
[15:58] <ahasenack> yeah
[15:58] <ahasenack> ok, it got to sshuttle
[16:01] <ahasenack> smoser: done https://code.launchpad.net/ubuntu/+source/sshuttle
[16:05] <rbasak> smoser: getting very close to that now.
[16:06] <rbasak> The importer concurrency is overhauled now, and is scaling nicely
[16:06] <rbasak> ahasenack: we could, though with the recent scaling improvements delays aren't really noticable for now except when doing things by hand
[16:07] <rbasak> There's also a big performance regression I know about that I want to fix, but I've been deferring it because it hasn't hit us in practice
[16:17] <znf> how do you set the DNS server on 18.04 when the interface has been configured trough /etc/network/interfaces ?
[16:17] <znf> dns-nameservers seems to be ignored in this case
[16:22] <znf> and there's no netplan, for some reasons
[17:46] <FunnyLookinHat> Ubuntu has (or still has?) the ability to create a user + shove an SSH key on them by default with an initial boot by placing a file in the filesystem somewhere... but I can't remember it for the life of me, and my googling is drawing a blank.  Anyone have any ideas?  More accurately, I think I remember it just putting a key into the ubuntu user's authorized_keys file maybe?
[17:55] <RoyK> !ansible
[17:56] <RoyK> FunnyLookinHat: just use ansible
[18:02] <FunnyLookinHat> LOL
[18:03] <FunnyLookinHat> Well I'm imaging some arm boards - like little r-pi's or whatnot - and I wanted to easily make the image shove some network config and an ssh key in.  I swear this was a part of the cloud init project or something
[18:03] <FunnyLookinHat> OH - Wow - CloudInit - That's the name...  apparently it was stuck in the back of my head: https://help.ubuntu.com/community/CloudInit
[23:18] <strixdio> I have ubuntu-server 20.04 running libvirt and lxc. network is configured with a bridge, static IP, no DHCP. Something is causing the boot to stall while "waiting for network". Any thoughts?
[23:20] <strixdio> I'd also like to add, I'm using pfSense as a VM, which obviously can't be on before the host.
[23:30] <RoyK> I'd suggest using an old PC of some sort for pfSense instead
[23:30] <RoyK> But apart from that, I don't know
[23:30] <strixdio> nah, looking for the power savings.
[23:31] <strixdio> I have a full rack of equipment and don't want much of it on 24/7. Then I can repurpose the current pfsense box as a test machine.
[23:31] <strixdio> I *think* /usr/lib/systemd/system/libvirtd.service "After=network.target" might be able to change, I have to see.
[23:33] <strixdio> idk if that is the answer I need though. I want to run a test to see if that's even what's causing it, first.
[23:35] <strixdio> yeah I think that wasn't the issue. How would I tell which service specifically is waiting for the network? "Reached target Host and Network Name Lookups" "A start job is running for wait for Network to be Configured"
[23:36] <strixdio> hypothetically the network *should* be configured with the static IP already, so I'm not sure why it's hanging.
[23:43] <sarnold> systemd has a boot analyzer that might help figure out which services is waiting for which other services