[00:02] https://paste.ubuntu.com/24377231/ are the new errors we get [00:36] powersj, i dont understand those E0702 [02:39] powersj, https://github.com/PyCQA/pylint/issues/1419 [17:05] rharper, fun bond fix spinoff [17:05] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1682871 [17:35] blackboxsw, are you actually doing the maas one ? [17:35] (bug 1677710) [17:35] thats great if you are. [17:36] * smoser hasn't had a maas around for a while. [17:39] smoser, yeah was going to give it a go [18:14] smoser: =( [18:14] I saw another thread about vlan_id=0 is somewhat undefined behavior [18:15] i didnt try anything other than xenial and yakkety [18:20] https://lwn.net/Articles/719297/ [18:20] 'In theory, VLAN 0 means "no VLAN". But the Linux kernel currently handles this differently depending on whether the VLAN module is loaded and whether a VLAN 0 interface was created. Sometimes the VLAN tag is stripped, sometimes not. [18:27] smoser, per 1677710, I deployed a xenial (!proposed) machine on maas 2.20rc1. I see the following in /run/cloud-init/ds-identify.log: [18:27] single entry in datasource_list (MAAS) use that. [18:27] [up 4.70s] returning 0 [18:27] hm.. [18:27] does this actually mean that ds-identify properly parsed the datasource? [18:28] no. it means the install only had that enabled [18:28] rharper, maybe you were missing that ? [18:28] rharper found this when doing some ubuntu core stuff [18:28] some versions of maas must pre-seed cloud-init with just MAAS [18:28] which, yeah, means that ds-identify shortcuts. [18:29] i had wondered why there wasnt much screaming over this [18:29] :) [18:36] what's going on ? [18:37] some versions of maas? how can it preseed the target? [18:39] through the cloud-inti preseed [18:39] I don't know what that is (ephemeral or deployment) ? [18:39] curtin passes the debian preseed through and dpkg-reconfigure [18:39] for *ubuntu* images [18:39] right. [18:39] deb-conf set selections work [18:39] and obviously that doesnt work for core images [18:39] the issue for the bug is for images that don't use debs [18:39] of course no one complained as no one is using core yet [18:39] well, yes. [18:40] but i didnt' realize it was was working still in ubuntu [18:40] you mentioned something that I missed ? [18:40] i didnt' think you understood it to be working in ubuntu either [18:41] ds-identify detecting maas in ubuntu images without the change to ds-identify to parse cloud.cfg.d/ ? [18:41] it entirely depends on where dpkg-reconfigure cloud-init wrote the cfg file [18:42] if it updates a file in /etc/cloud/*maas*.cfg; and had MAAS in the file, it would work; the issue was that it didn't search the cloud.cfg.d/*.cfg [18:45] hm.. [18:45] oh [18:45] no [18:45] oh. so it was busted. and blackboxsw verified it fixed. [18:45] they use pxe kernel cmdline, right ? [18:45] in addition to the cloud config [18:45] i didnt' realize blackboxsw above said proposed [18:45] they had two possible paths to tell it [18:45] for ephemeral they do cmdline [18:46] and it worked there. [18:46] right [18:46] but was busted in install images. [18:46] but i'm confused why there wasnt more screaming. [18:46] hrm [18:46] wasnt/isnt/ [18:46] oh. [18:46] i know [18:46] it was just yakkety that was busted [18:46] xenial is report only [18:46] yes [18:46] that's right [18:46] so it'd say it found nothing but then work anyhow [18:46] ie, not disable itself [18:47] that doesn't quite line up with saying it found MAAS though [18:47] I'd be happy to see /run/cloud-init/* and /etc/cloud/* [18:47] from that instance [18:47] then we can sort out what it did and did not find [18:49] ? [18:49] in above, it found a single datasource configured (MAAS) [18:49] which indicates it searched /etc/cloud.cfg.d/ [18:49] blackboxsw, you could pastebin /run/cloud-init/ds-identify.log [18:53] blackboxsw, ahasenack thanks. you guys have been a huge help [18:54] smoser: the newer code does [18:54] he said !proposed [18:54] so that'd be the previous one, right ? [18:54] which didn't search cloud.cfg.d [18:57] i dont know [18:57] i dont know how it could work. [18:57] i'd like to see more. [18:58] * smoser really wishes he had a maas again [18:58] i do intend at some point to get beisner's work up joined with some updated "virtual-maas" stuff [18:58] so that we can easily deploy a maas on diglett [18:59] well, I know it didn't search the .cfg dir before; the code was pretty clear about what files it searched [18:59] what's not clear is what cloud-init was tested in the above report [18:59] report [18:59] supposedly not the proposed one [18:59] but we'll need the log and cloud dirs [19:00] hey. i'm out. have a nice weekend all. [19:00] ok [19:00] you too [19:07] sorry smoser got pulled into a phone call. [19:07] geting that now [19:08] http://paste.ubuntu.com/24382246 [19:11] * blackboxsw catches up on backlog. So yeah I had a maas 2.2.0rc1 available and when I deploy xenial to bare metal I didn't see any warnings on login about missing datasources per 1677710. I didn't tweak anything in preseeds on this install as I wanted/hoped to see the original failure mode [19:12] this is commandline login BTW I don't have physical access to the hardware [19:15] grabbing cloud-init/* and /etc/cloud/* [19:20] rharper, for future reference on this one http://paste.ubuntu.com/24382309/ here are my /var/cloud-init/* files . I'll keep poking at this [19:21] I had tested xenial (not xenial-proposed). ii cloud-init 0.7.9-48-g1c795b9-0ubuntu1~16.04.1 all Init scripts for cloud instances [19:22] blackboxsw: can you paste "find /etc/cloud" [19:22] /etc/cloud/cloud.cfg.d/90_dpkg.cfg set datasource_list: [ MAAS ] [19:23] grabing that too. http://paste.ubuntu.com/24382329/ [19:24] there may be some issues here with report mode vs the strict handling [19:25] http://paste.ubuntu.com/24382335/ [19:25] ^ /etc/cloud/cloud.cfg.d/90_dpkg_maas.cfg with keys redacted [19:25] ok. that makes sense. [19:25] it always read that file [19:25] and maas seeded cloud-init with that so it wrote it. [19:25] /etc/cloud/cloud.cfg.d/90_dpkg.cfg [19:25] later [19:26] cat /etc/cloud/cloud.cfg.d/90_dpkg.cfg [19:26] # to update this file, run dpkg-reconfigure cloud-init [19:26] datasource_list: [ MAAS ] [19:27] have a good one smoser