[16:05] smoser: pushed my functional code to https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+ref/feature/os-local I had to back out some wip stuff. tested on serverstack. I'm thinking of moving the fallback_nic property up to base Datasource and adding some additional error checking on metadata type === blackboxsw changed the topic of #cloud-init to: Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting: Monday 4/23 16:00 UTC | cloud-init 18.2 released (03/28/2018) [16:30] aaaahhhhh :) [16:30] analyze.local:Total Time: 7.48900 seconds [16:30] analyze.net:Total Time: 17.32100 seconds [16:30] 10 second saved on openstack boots :) [16:46] \o/ [17:29] it seems as though the most important of my fixes landed a day too late to be included in the latest xenial and artful packages, at least according to https://launchpad.net/ubuntu/+source/cloud-init. When is the next chance for them to be picked up? [17:31] mgerdts: sorry that was a 2 week process for the SRU xenial/artful. we'll probably be handling another sru within a month as we'll be publishing more content into Bionic too I imagine [17:32] and we'll have to SRU into bionic too at that point [17:32] ok. Will artful get another update? Or will it be sufficiently aged by then that it's no longer supported? [17:33] mgerdts: https://wiki.ubuntu.com/Releases [17:33] artful will go EOL in July. [17:33] smoser: rharper can you confirm. I thought there would be a window for a while where xenial, artful and bionic are all SRU'd to. [17:33] thanks smoser [17:33] yep [17:34] per /usr/share/distro-info/ubuntu.csv 2018-07-19 [17:34] once bionic is out, artful is not very interesting. [17:34] (that's our general experience) [17:34] dpb1: but stable release update process requires you to do the srus there also [17:34] yes, I understand [17:35] blackboxsw: http://hangouts.google.com/hangouts/_/canonical.com/cloud-init have a minute ? [17:36] % distro-info -y --days=eol --all -r | grep -v -- - [17:36] 14.04 LTS 359 [17:36] 16.04 LTS 1094 [17:36] 17.10 87 [17:36] 18.04 LTS 1829 [17:36] [17:36] fancy [17:37] Oh, once I finally mapped out the release names in my head you show me something that has release numbers. :) [17:37] hehe [17:38] % distro-info -y --days=eol --all -f | grep -v -- - [17:38] Ubuntu 14.04 LTS "Trusty Tahr" 359 [17:38] Ubuntu 16.04 LTS "Xenial Xerus" 1094 [17:38] Ubuntu 17.10 "Artful Aardvark" 87 [17:38] Ubuntu 18.04 LTS "Bionic Beaver" 1829 [17:38] :) [17:38] * rharper adds a new tool to the chest [17:39] https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766302 [17:39] Ubuntu bug 1766302 in cloud-init (Ubuntu) "netdev_pformat does not show unconfigured devices" [Undecided,New] [17:39] Is this one expected to be in the GA build of bionic? https://launchpad.net/ubuntu/+source/cloud-init/18.2-14-g6d48d265-0ubuntu1 [17:40] http://paste.ubuntu.com/p/BmkH37g9qf/ [18:04] mgerdts: yep. that's in : rmadison cloud-init tells you the released versions of a pkg [18:04] http://paste.ubuntu.com/p/35zrnQPZCY/ [18:05] thanks [18:05] no problem, it's in devscripts deb if you a frequent need for rmadison find you need [18:06] sorry, typo-central. [18:08] n [18:22] o.O [18:42] Hi @bloackboxsw, I'm Josh a new dev from Azure. I was wondering if you could take a look at my merge request : https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/343563 :) [18:43] welcome jocha. sure can look it over today [18:44] was in a bit of an Ubuntu-release mode last week, will get through some reviews [18:45] awesome! Thanks! [19:42] Is `cloud-init collect-logs` expected to work when run inside a chroot? I get the following errors https://pastebin.ubuntu.com/p/wRvgGZ6HnR/ [19:44] interesting philroche, hadn't tried that use-case. I presume it doesn't given that your chroot's rundir would be different. [19:44] I think it's worth a bug... [19:44] here's what it tries to grab for you [19:44] blackboxsw: ack [19:44] http://cloudinit.readthedocs.io/en/latest/topics/capabilities.html#cloud-init-collect-logs [19:45] blackboxsw: That's the exact link I was looking for :) [19:45] I'll take off my mind-reading glasses now to save them for a better time [19:47] :) [19:59] blackboxsw: Bug filed - https://bugs.launchpad.net/cloud-init/+bug/1766335 [19:59] Ubuntu bug 1766335 in cloud-init "Running cloud-init collect-logs inside a chroot is not possible" [Undecided,New] [19:59] thank you sir [20:01] philroche: frequently I like to see /run/cloud-init/instance-data.json as it tells us what the datasource gives us as far as metadata and userdata etc. but judging from your chroot, that no longer exists. [20:02] blackboxsw: Yes, that no longer exists [20:03] blackboxsw: well thats on /run which is memory only. [20:03] bummer, ok. I'll work on making collect-logs more resilient in a chroot today/tomorrow. So at least we can collect some remnant of the files around [20:04] smoser right, but we also have symlinks to files that should still exist, which we could pull, like status.json -> ../../var/lib/cloud/data/status.json and result.json. But, cloud-init.log and journalctl would give us the content of those files at least. [20:33] Is there any special way that I should poke redhat or others to get my fixes into rhel 7 and/or centos 7? [20:51] mgerdts: not sure, we might have representatives in next week's #cloud-init status meeting on Monday per topic in this IRC channel. larsks (IRC nick) might have info on where to start if he joins in . [20:52] ok, thanks. What time is that meeting at? [20:52] Monday 4/23 16:00 UTC [20:52] thanks [20:52] oops [20:52] 4/30 :0 [20:52] yeah. :) [20:53] I mis-set the date this morning :/ [20:53] #topic #cloud-init Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting: Monday 4/30 16:00 UTC | cloud-init 18.2 released (03/28/2018) [20:53] ok fixed === r-daneel_ is now known as r-daneel [22:17] rharper: looks like we call it fallback_nic twice : http://paste.ubuntu.com/p/zMkBd8hWbW [22:18] * blackboxsw creates a bootable image from this [22:23] interesting