[04:54] jocha: initial review posted for tomorrow https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/343563 [04:55] and I'm outta here === r-daneel_ is now known as r-daneel [16:49] blackboxsw: https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/343127 could use a review if you were bored [16:49] looking [16:49] was just trying to spawn a failed instance on gce [16:49] * blackboxsw was working through capturing an image and booting a new instance with it [16:49] with serial console ? [16:49] as we'll need to do that inevitably if we can find a reproducer [16:50] yeah trying with serial console + root password backdoor and custom cloud-init [16:50] cool. [16:52] I'll wrap up the gce instance from image spawn on cmdline and add a placeholder script to qa-scripts/scripts/launch-gce. then I'll grab that review, sound good as far as priority? [19:19] smoser: hrm, we actually have a run-time depends on iproute2 ; for the minumal cloud-images, there's no iproute2 in that even though it has cloud-init, the fallback nic code runs ip route commands; which it doesn't find; in ubuntu/devel branch the control file does not include iproute2; [19:27] http://paste.ubuntu.com/p/87ZhVjWjMW/ [19:27] rharper: not a huge deal [19:27] its part of ubuntu-minimal [19:27] which .... should be part of ubuntu "minimal" image :) [19:28] so yes, we could add it and possibly should add it. but its goign to be there. [19:28] and that is the case for xenial also [19:30] well, http://cloud-images.ubuntu.com/minimal/daily/bionic/ those are all broken w.r.t not having iproute2 in it [19:32] smoser: rharper by add it, you mean an 'or' depends on iproute2 or net-tools? [19:32] or an explicit iproute2 dep in bionic & later [19:32] explicit, depite the net banner, fallback nic configuration uses the 'ip' command [19:33] blackboxsw: well, at this point i'd chagne upstream packaging to just say iproute2 [19:33] but would leave x, a, b as they are [19:33] ok fair 'nuf [19:34] rharper: why would we create something with the name 'ubuntu' and 'minimal' that did not have 'ubuntu-minimal' [19:34] :-( [19:34] (╯°. °)╯︵ ┻━┻) [19:35] even stating: [19:35] It is also used to help ensure proper upgrades, so it is recommended that [19:35] it not be removed. [19:39] smoser: you have a few hours to listen to the story about names? [19:40] smoser: if you want a fun time, click https://askubuntu.com/questions/tagged/ubuntu-minimal, which is a combination of questions about the mini iso and the minimal desktop. [19:41] just FYI, I'm able to spawn gcloud instances based on an image w/ updated cloud-init ( which logs gcloud compute instances create image-test2 --zone=us-central1-b --image upgraded-cloud-init-disk --image-project cloud-init-testing --metadata-from-file user-data=sethostname.yaml --metadata=serial-port-enable=1). I'm dropping this stuff into qa-scripts/scripts/launch-gce now [19:41] still no reproducer on my end [19:43] I'm both happy and sad by that news [19:44] blackboxsw: thanks [19:44] I'll use that [20:03] https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766711 [20:03] Ubuntu bug 1766711 in cloud-init (Ubuntu) "cloud-init missing dependency on iproute2" [Undecided,New] [20:14] bug https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1766714 [20:14] Ubuntu bug 1766714 in cloud-init (Ubuntu) "cloud-init missing dependency on isc-dhcp-client" [Undecided,New] [20:24] ugh, though I placed it in Package: cloud-init [20:24] Architecture: all [20:24] Depends: ${misc:Depends}, [20:24] ${${python}:Depends}, [20:24] isc-dhcp-client [20:24] in packages/debian/control.in [20:25] s/I/we/ [20:33] thats for trunk packaging . i probably blame to the foobar on the ubuntu/devel branch [20:53] blackboxsw: [20:53] https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344186 [20:54] https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344186 [20:54] https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344190 [20:54] smoser: you have a few minutes to sync on the rename stuff? [20:54] rharper: sure. [20:54] https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344181 [21:12] smoser: approved and landed https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344190 [21:12] approved https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/344186... will land it [21:16] smoser any more thoughts on https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/343712 . Was just chatting on #smartos where one of our early adopters was surprised that a NIC that he added after the first boot did not get configured on a subsequent boot. [21:21] smoser: I'm not merging https://code.launchpad.net/~vkuznets/cloud-init/+git/cloud-init/+merge/343601 at the moment. as I didn't want unnecessary churn on the bionic branch we want to cut [21:22] blackboxsw: you're still working on the recreate? [21:22] on gce ? [21:23] * smoser out [21:23] rharper: I haven't recreated, but I can continue to spin instances up using and updated cloud-init that tracks name_assign_type [21:23] rogjt mpw O [21:23] right now I'm merging in smoser's bionic fixes [21:23] blackboxsw: ok; I think we have a more general solution here w.r.t the the renaming; [21:23] and generating a bionic upload mp which includes isc-dhcp-client dependencies [21:24] y [21:24] blackboxsw: I've resolved the comments you made, feel free to review whenever you have time :) https://code.launchpad.net/~jocha/cloud-init/+git/cloud-init/+merge/344192 [21:26] did you push the launch-gce script to qa-scripts ? [21:26] rharper: noper. it's a big lift [21:26] I'd like to see if I can fire up a loop to trigger the failure [21:26] I'm re-writing a lot of launch-ec2 at the moment [21:26] can you pastebin it to me (no without creds) ? [21:27] I guess I can just use your gcloud command from earlier [21:27] rharper: as in, not even functional. I'll give you a pastebin of the commands I run on gcloud [21:27] yeah, thanks [21:27] will work on a reproducer loop there; with root login on serial console; [21:35] rharper: here's the basics https://pastebin.ubuntu.com/p/xHgHRY3vbt/ [21:35] thx [21:36] it involved me having installed google-cloud-sdk [21:36] I think there was some setup there [21:36] yeah [21:36] I have that installed [21:36] I see your ssh pubkeys are part of our project so that should be good [21:37] in that pastebin I forgot the addition commands to dpkg -i cloud-init*deb; cloud-init clean --logs; and sudo passwd ubuntu setup before stopping the instance and creating an image [21:37] yeah; mostly wanted the instance image and type details and that serial port bit [21:38] is there a gcloud command for getting the console ? [21:43] rharper: with that metadata serial-port-enable=1 stuff you can then cloud compute connect-to-serial-port bionic-test [21:43] rharper: with that metadata serial-port-enable=1 stuff you can then "gcloud compute connect-to-serial-port bionic-test" [21:43] nice [23:18] blackboxsw: smoser: ok; I've recreated, updated the bug with details for possible fix and how to test it; https://bugs.launchpad.net/cloud-init/+bug/1766287 [23:18] Ubuntu bug 1766287 in cloud-init "18.04 minimal images on GCE intermittently fail to set up networking " [High,New] [23:31] rharper: nice, so maybe it was region related then ? I see you switched to europe-west1 [23:31] yes [23:31] and back to the 420 image [23:31] man. [23:31] I've not tried on the 421 [23:31] but I suspect that europe-west1 is just less crowded [23:31] also, it's night time now [23:31] I'll give that a spin tonight if you are about EOD. [23:31] now that I have the recreate, I'll try again in other zones [23:31] nice [23:32] k back in an hour [23:32] k