=== cpaelzer__ is now known as cpaelzer
Odd_BlokeI'm looking at https://bugs.launchpad.net/cloud-init/+bug/1843221 for triage, and I'm not sure what to recommend the user do.  They're using NoCloud, so I think they probably could specify network config, but am I missing a way for a user without that option to configure DNS in a system?14:41
ubot5Launchpad bug 1843221 in cloud-init "manage_resolv_conf not working in ubuntu18.04 cloud images" [Undecided,New]14:41
smoserOdd_Bloke: i think that was teh right answer15:01
Gonerihey, could you please take a look at https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507 and https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/36564115:54
Odd_Blokerharper: Looks like you've reviewed those two branches previously.15:55
blackboxswannnd it's that time for real: cloud-init status meeting.16:25
blackboxsw#startmeeting Cloud-init bi-weekly status16:26
meetingologyMeeting started Mon Sep  9 16:26:10 2019 UTC.  The chair is blackboxsw. Information about MeetBot at http://wiki.ubuntu.com/meetingology.16:26
meetingologyAvailable commands: action commands idea info link nick16:26
blackboxswHey folks, welcome to the ~biweekly cloud-init status meeting.16:27
blackboxsw#chair rharper Odd_Bloke16:28
meetingologyCurrent chairs: Odd_Bloke blackboxsw rharper16:28
blackboxswcloud-init upstream uses this meeting as a platform for community updates, feature/bug discussions, and an opportunity to get some extra input on current development.16:28
blackboxswFeel free to interject at any time. Our typical format is the following:  Previous Actions, Recent Changes, In-progress Development, Office Hours (~30 mins)16:30
blackboxswLast meeting's minutes live here:16:30
blackboxsw#link https://cloud-init.github.io/status-2019-08-19.html#status-2019-08-1916:30
blackboxsw#topic Previous actions16:30
blackboxswno actions from last meeting so we'll plow right through to Recent Changes16:31
blackboxsw#topic Recent Changes16:31
blackboxswThe following branches have landed in tip since last meeting: via    git log --since 2019-08-1916:32
blackboxsw    - doc: document doc, create makefile and tox target [Joshua Powers]16:32
blackboxsw    - .gitignore: ignore files produced by package builds [Daniel Watkins]16:32
blackboxsw    - docs: fix whitespace, spelling, and line length [Joshua Powers]16:32
blackboxsw    - docs: remove unnecessary file in doc directory [Joshua Powers]16:32
blackboxsw    - Oracle: Render secondary vnic IP and MTU values only [Ryan Harper]16:32
blackboxsw    - exoscale: fix sysconfig cloud_config_modules overrides16:32
blackboxsw      [Chad Smith] (LP: #1841454)16:32
ubot5Launchpad bug 1841454 in cloud-init "Exoscale datasource overwrites *all* cloud_config_modules" [Undecided,Fix committed] https://launchpad.net/bugs/184145416:32
blackboxsw    - net/cmdline: refactor to allow multiple initramfs network config sources16:32
blackboxsw      [Daniel Watkins]16:32
blackboxsw    - ubuntu-drivers: call db_x_loadtemplatefile to accept NVIDIA EULA16:32
blackboxsw      [Chad Smith] (LP: #1840080)16:32
ubot5Launchpad bug 1840080 in cloud-init (Ubuntu) "cloud-init cc_ubuntu_drivers does not set up /etc/default/linux-modules-nvidia" [High,Fix released] https://launchpad.net/bugs/184008016:32
blackboxsw    - Add missing #cloud-config comment on first example in documentation.16:32
blackboxsw      [Florian Müller]16:32
blackboxsw    - ubuntu-drivers: emit latelink=true debconf to accept nvidia eula16:32
blackboxsw      [Chad Smith] (LP: #1840080)16:32
blackboxsw    - DataSourceOracle: prefer DS network config over initramfs16:32
blackboxsw      [Daniel Watkins]16:32
blackboxsw    - format.rst: add text/jinja2 to list of content types (+ cleanups)16:32
blackboxsw      [Daniel Watkins]16:32
blackboxsw    - Add GitHub pull request template to point people at hacking doc16:32
blackboxsw      [Daniel Watkins]16:32
blackboxswAdditionally: we have also cut a stable-18.4 branch from the 18.4 tag as our last supported python2.6 branch. There will be an email sent out to the mailing list about the intent of this branch.  It requires a couple of minor fixes to make sure py2.6 support is functional, but this will be reference branch for any distribution that does not have access to py.27 or later.  No additional feature development is16:34
blackboxswplanned on stable-18.416:34
blackboxswa reminder again that python2.6 support was 'dropped' in cloud-init upstream as of the 18.4 release, so expectations for py2.6 support stopped  in 18.4 and there is a deprecation plan for py 2.7 as well16:37
blackboxsw#link https://lists.launchpad.net/cloud-init/msg00170.html16:37
blackboxswAgain, see the mailinglist for details and updates16:37
blackboxsw#link https://lists.launchpad.net/cloud-init/16:37
blackboxsw#topic In-progress Development16:38
blackboxswLast week or so the team has been working on SRU validation for cloud-init 19.2.24 into Xenial, Bionic and Disco.16:38
blackboxswWe have passed all SRU validation tests and our expected pubish date for 19.2.24 is tomorrow for those Ubuntu series16:39
blackboxswgood work on validation folks16:40
blackboxswand thanks for extra cloud-init community verification from exoscale, azure and VMware for validation efforts16:41
blackboxswThere is additional Oracle, FreeBSD and Azure work in flight at the moment as well as some boot speed improvements and analysis from rharper16:42
blackboxswThe following link represents any carded work upstream is  tracking. The Doing lane is content or features we expect to land shortly16:43
blackboxsw#link https://trello.com/b/hFtWKUn3/daily-cloud-init-curtin16:43
blackboxswNow is probably a good time to also mention that our entire ubuntu server team also reflects our weekly accomplishements over in the ubuntu-server discourse. If there are deeper discussions or questions on various topics or features please join us there as well16:47
blackboxsw#link https://discourse.ubuntu.com/c/server16:47
blackboxswI think that about wraps it for in-progress development16:48
blackboxsw#topic Office Hours (next ~30 mins)16:48
blackboxswupstream cloud-init devs will have eyes on this channel for any discussions, questions, bugs or feature work the greater community would like to discuss.16:48
blackboxswDuring this time, we'll also groom our activereview queue to make sure we try to get review comments out to devs who have active branches.16:49
blackboxswAgain, thanks for tuning in16:49
blackboxswOk just addressed review comments on https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/372432 .   I'm reviewing https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/36850716:57
* blackboxsw also sets the next meeting topic so we don't forget.16:59
blackboxswOdd_Bloke: rharper powersj, I *think* we decided to shift from Mondays to Tuesdays for status meetings to avoid collisions with holidays, vacation work travel etc. Are we doing that for next status meeting, or maybe waiting to discuss that more broadly?17:01
Odd_BlokeTuesday in two weeks is likely to be a travel day for anyone heading to the cloud-init summit.17:02
Odd_BlokeBut Monday is likely to be a swap day for Canonical folks because we're all travelling next week too.17:02
blackboxswhrm right, maybe we wait then and discuss at the summit17:03
Odd_BlokeSo I would perhaps suggest skipping the next meeting, and then we can resume on Tuesdays two weeks after the summit?17:03
blackboxswdiscuss scheduling changes that is17:03
blackboxswsure, let's push/postpone until summit +2 weeks17:03
=== blackboxsw changed the topic of #cloud-init to: Reviews: http://bit.ly/ci-reviews | Meeting minutes: https://goo.gl/mrHdaj | Next status meeting Oct 8 16:15 UTC | cloud-init v 19.2 (07/17) | https://bugs.launchpad.net/cloud-init/+filebug
blackboxsw#action blackboxsw send email to the list notifying of status meeting day change.17:05
meetingologyACTION: blackboxsw send email to the list notifying of status meeting day change.17:05
rharper+1 Odd_Bloke17:10
blackboxswAlso note that the version of cloud-init that has undergone SRU verification is also published to our copr el-testing repo. We only update that repo during upstream cloud-init releases XX.YY and any Ubuntu SRUs so it is much more stable than our daily copr repo.17:11
blackboxsw#link https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/17:11
blackboxswI think that about wraps our cloud-init status meeting for today. I'm wrapping up my review here and will post it to the set_passwords branch.17:33
meetingologyMeeting ended Mon Sep  9 17:33:31 2019 UTC.17:33
meetingologyMinutes:        http://ubottu.com/meetingology/logs/cloud-init/2019/cloud-init.2019-09-09-16.26.moin.txt17:33
blackboxswminutes published to https://cloud-init.github.io/status-2019-09-09.html#status-2019-09-0917:35
blackboxswthanks folks17:35
Odd_Blokeblackboxsw: Thanks for running the meeting!18:02
blackboxswOdd_Bloke: no prob18:05
blackboxswrharper: Goneri I finished my review of https://code.launchpad.net/~goneri/cloud-init/+git/cloud-init/+merge/368507 a couple comments/suggestion inline  for you both to weigh in on. thanks again18:06
smoserOdd_Bloke: sorry, do we use 'Fixes LP: #XXXXX' now ?18:06
blackboxswI'm +1 on that approach but had a couple of suggestions18:06
smoserin your commit message. versus just ^LP: #XXXXX18:06
blackboxswsmoser: Odd_Bloke haha that is because Dan's mind is doing github branches for ubuntu-advantage-tools18:07
blackboxswcloud-init should be just LP: #XXX18:07
Goneriblackboxsw, great, I will address that ASAP.18:07
Odd_BlokeYeah, that's GitHub leaking.18:11
ozzzoWhen I install cloud-init on RHEL 5.7 it throws URL errors and then fails:18:12
ozzzo2019-09-06 14:42:28,584 - DataSourceEc2.py[WARNING]: '' failed [3/120s]: url error [[Errno 113] No route to host]18:12
ozzzoIn /etc/rc.d/init.d/cloud-init I see it trying to read /etc/sysconfig/cloud-init which doesn't exist18:13
ozzzodoes that mean I screwed up the install?18:13
Odd_Blokeozzzo: Where did you install it from?18:13
ozzzorpm -ivh /u/yesuv/Downloads/epel-release-5-4.noarch.rpm18:14
ozzzoyum install -y cloud-init18:14
Odd_Blokeozzzo: What does `cloud-init --version` give you?18:15
ozzzo[root@image-qscl-rh57 sysconfig]# cloud-init --version18:15
ozzzobad command --version. use one of ('start', 'start-local')18:15
Odd_BlokeOK, I think that means that's an ooold version of cloud-init (which probably isn't a surprise in RHEL 5! :).18:17
blackboxswyeah even 0.7.9 has a cloud-init --version command :/18:17
ozzzois 5.7 too old to run cloud-init?18:18
ozzzowe're being asked to provide 5.7 VMs to save developers from having to upgrade their code18:19
Odd_BlokeThe honest answer from me is that I'm not sure.18:20
ozzzoWhat problem is it reporting? Does cloud-init require some kind of support service that works across the 169 network?18:21
ozzzocan I fix it by setting up something to answer the metadata request?18:22
Odd_BlokeWell, it's trying to talk to the Amazon EC2 metadata servers, and not able to route to them.18:22
Odd_BlokeBut, honestly, the version you're running is so old that I don't know what else is supported.18:23
blackboxswozzzo: if you are trying to buildimages might want to look at building or installing the latest cloud-init RPMs in https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/   but yeah per Odd_Bloke's comment, your image isn't contacting Ec2 urls for some reason18:23
rharperI suspect it's missing networking config in the image;  you could try our cloud-init in the el-stable copr repo,18:23
rharperblackboxsw: I think for RHEL5.x they might need the older release18:23
Odd_BlokeYeah, I think RHEL5 is Py 2.4 or Py 2.5.18:23
blackboxswas in pre-py26?18:23
ozzzoI'm not in AWS; is this early version of cloud-init designed to only work in AWS?18:23
rharperthat's known to work on Centos6;  might be old enough, but have the networking features needed to bring up network for an ec2 crawl18:24
ozzzowe're setting up openstack VM images18:24
rharperozzzo: no, there are many datasources, openstack also uses the same metadata URL18:24
rharperI suspect that the image doesn't have any build-in network config (like a /etc/sysconfig/network-scripts/ifcfg-eth0 which is configured to dhcp);18:24
ozzzoI don't think I can reach a 169 IP across the internet; that network doesn't route18:24
ozzzoit seems like I would need a server on my local network to answer that request18:25
rharperand so cloud-init will try to talk (over network) to different endpoints to determine if it's running on a particular cloud type18:25
rharperthere are other datasources, like NoCloud which can use a localally attached disk with configuration in it18:25
ozzzoso I can setup nocloud and then configure cloud-init to use that instead of 169?18:26
rharperyes, https://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html18:27
Odd_BlokeWell, in an OpenStack cloud there should still be something on, right?18:27
Odd_BlokeOr it should be using ConfigDrive.18:27
rharperI suspect ozzzo is booting outside of the cloud18:27
Odd_Blokeozzzo: Are you testing your images in the environment you expect them to run, or just locally?18:27
rharperto test the image , is that right ?18:27
ozzzoThis is a VM image; I'm just building it18:27
ozzzoyes, in the VM environment, there may be something listening on 16918:28
ozzzowe're building the images on VMWare18:28
rharperyou may find that the image will work fine inside the openstack environment;  testing your local imge with NoCloud is a reasonable first step to see if cloud-init you put in the image is working.18:30
ozzzook I'll try it, thanks for the advice18:30
rharperOdd_Bloke: blackboxsw: I can't sort out why the autoland is failing on pycodestyle ... thoughts?  https://jenkins.ubuntu.com/server/job/cloud-init-autoland-test/315/console18:32
rharperI've run tox and tox -e tip-pycodestyle  with no issues;  it's complaining about 3 new lines where there should be two, but the file in the repo is good to go18:33
Odd_BlokeYeah, I can't see why either.18:44
Odd_Blokerharper: Are you on bionic?18:53
Odd_Bloke(I'm wondering if it's a Py 3.6 issue?)18:53
rharperno, xenial18:53
rharperbut I can try on bionic18:53
ozzzowe're running cloud-init 0.6.3-0.12.bzr532.el519:06
ozzzoI'm going to try ignoring the cloud-init error on the image, finish building it, and then build OS VMs to see if cloud-init works there19:07
rharperOdd_Bloke: I needed to rebase, now I see it and removing the extra line, force push should fix here shortly20:01
Odd_BlokeSo the extra line was showing up in the merge commit?20:06
rharperI didn't realize I was not rebased to tip20:07
Odd_BlokeWow, good job on finding that.20:08
Odd_BlokeI think I'd just be unconscious from banging my head on things.20:09
rharperI was for a bit in a bionic container20:10
rharperbut now I've got a bitter headache in #curtin20:10
rharperbigger (and bitter)20:10
rharperblackboxsw: ok, I re-approved my netfailover branch after the force push, hoping that the autolander will be happy now20:54

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!