/srv/irclogs.ubuntu.com/2017/04/11/#cloud-init.txt

sambettsHi cloud-init team, I have recently been experimenting with cloud-init 0.7.9 and Centos to try to make OpenStack network_data.json work and it seems I've found and issue when processing bonded interfaces in the sysconfig renderer, what is the process for getting this resolved? and/or how can I contribute?10:51
=== shardy is now known as shardy_lunch
=== shardy_lunch is now known as shardy
smosersambetts, please open a bug if you dont see any existing.13:29
smoserif you're looking at helping out, https://github.com/openstack/cloud-init/blob/master/HACKING.rst13:30
smoserpowersj, just a utility.13:30
smoserideally i think that functionality gets into cloud-init as a sub command.13:30
sambettssmoser: is the openstack/cloud-init repo the right repo to commit too? That repo is out of date with the launchpad.net one, launchpad is one 0.7.9 the openstack/cloud-init repo is only on 0.7.614:25
smosershoot14:25
smoseri gave bad uurl14:25
smoserfollow HACKING. there is a push mirror of launchpad on github14:26
smoser https://github.com/cloud-init/cloud-init/commits/master14:26
smoserbut the openstack/cloud-init should probably get deleted.14:26
smoserhttps://github.com/cloud-init/cloud-init is the github, but launchpad is where merge proposals are done so really use that.14:26
smosermake sense ?14:27
sambettsYup thanks! whats the release process for cloud-init, e.g. if a bug fix goes in how long does it take to get tagged?14:30
smoserwell... it has varied a lot :)14:33
smoserbut recently coming more frequently, and i'd really like to be in the realm of 3 months or less between releases.14:34
smoserwe are nearing one now.14:34
smoserutlemming, i'm around if you want to chat some about your MPs14:34
sambettsawesome :) whats the cloud-init project's relationship with packaging? I noticed that the version included on centos7 is quite old14:36
utlemmingsmoser: yup, I'm here14:40
smosersambetts, larsks i think is the best contact with centos packaging. We're working on getting integration tests flushed out so we can run tests on centos and such.14:41
smoserand would like to get closer to sane packaging available in trunk so that i was easier for maintainers.... not sure if thats totally possible or desireable though14:41
sambettsmakes sense, thanks for answering my questions, hopefully I can get permission to contribute to the project :)14:42
utlemmingI also filed this little gem: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/168153114:46
utlemmingI was planning on taking a look at it later today. tl;dr is network.service fails because the nic's have been ifup'd already14:46
utlemming(just realized that ifup'd looks like a dirty word...)14:46
=== jgrimm is now known as jgrimm-away
smoserutlemming, cloud-init should not 'ifup'... did you see it specifically doing that ?16:25
utlemmingsmoser: yup16:27
utlemmingsmoser: pulliung a log now16:27
smoserpowersj, https://bugs.launchpad.net/cloud-init/+bug/163653116:57
powersjsmoser: yes16:57
smosercan you recreate that?16:57
powersjif I modify my path then yes16:58
smoseri think ideally we're not calling blkid... but even then if we are, id' like to know what your change was there16:58
smoseryou said what you set it *to*16:58
powersj:/sbin: is what was added16:59
smoserodd that that was not in your path17:00
smoserthat is almost a bug itself17:00
smoserie, ubuntu has /sbin in path by default, so s390x ubuntu *not* having it is just asking for other people to find that17:01
smoserdont worry about recreate, powersj : http://paste.ubuntu.com/24361950/17:01
powersjsmoser: I wouldn't say it was an ubuntu thing, rather a jenkins not having /sbin in the path by default17:02
smoserif you made that change on alkl other jenkins, then i agree. but one should typically not have to set PATH ... why would jenkins not just inherit its default PATH as your user does ?17:04
powersjsmoser: I did update all slaves to that path as I put in the bug. the slaves run by default on a more limited path, I'm trying to find the default17:10
=== sambetts is now known as sambetts|afk
utlemmingsmoser: three MP's that break up the imrpovments for DigitalOcean. One for the resolvers, one for configuring all Nics, and one for the NIC userd for the meta-data selection. All tested and confirmed to work.17:25
smoserutlemming, do those overlap too much to submit them without the others ?17:34
smoseri have comments on each17:34
smoserand the second and third have the first 2 so reading the diff is combined rather than individual17:35
utlemmingsmoser: the first two definately overlap17:37
utlemmingI can break the third up17:38
smoserdo you know how this affects sysconfig rendering ?17:38
utlemmingI don't....but I suspect that it will fix some of the problems that I've seen. I can try and get a test fix. Right now only Ubuntu and Debian use that DS for now.17:40
smoserpowersj, https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/32238618:07
powersjsmoser: I like it, thank you18:10
utlemmingsmoser: https://code.launchpad.net/~utlemming/cloud-init/+git/cloud-init-1/+merge/322385 is broken out from the others. Nice and clean.18:17
smoserutlemming, i'm not sure ifindex is what you want18:20
smoserhttps://www.kernel.org/doc/Documentation/ABI/testing/sysfs-class-net18:20
smoseri dont see any indication on order or anything18:21
utlemmingsmoser: in testing it, it represent the device order....starting with lo being 0, and ens3 being 1.18:24
* utlemming digs further on it18:24
utlemmingsmoser: I actually think that its safe. The ifindex is incremented by 1 as the devices are added, regardless of the name. Since we are on the virtio-bus and there is a check to make sure that the interface is physical, the first nic will always have a lower index, even if its not 1.18:32
utlemmingi.e. if a user has defined 'dummy0' it wouldn't be a phyisical nic and therefore excluded from the check.18:32
=== mgagne_ is now known as Guest89317
smoserrharper, ^ ? we were trying to kind of use ifindex to indicate order on the virtio bus18:37
smoserutlemming, you have an instance up that i can ssh into ?18:38
smoseror shall i launch one on digital ocean18:38
utlemmingsmoser: root@138.197.119.11818:39
=== mgagne_ is now known as Guest4366
=== Guest4366 is now known as mgagne
smoserutlemming, where did you find '-1' ?19:30
smoserutlemming, http://paste.ubuntu.com/24362776/19:40
smoserthat is basically "get nic with lowest ifindex". although i' still not sure if that is the right thing.19:40
smoserpowersj, would you +1 https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/322386 ?19:41
powersjsmoser: done19:42
utlemmingsmoser: -1 was to indicate that a nic hadn't been tested yet19:57
utlemmingsmoser: +1 on that....its clean19:58
smoserutlemming, so update your MP then with that... and i guess drop the 'LOG.warn' that i added, just return None.19:59
smoseras the caller there is going to raise RuntimeError20:00
utlemmingsmoser: ack, doing so now20:00
cmartHi folks - I'm troubleshooting a particular OpenStack image that runs cloud-init 0.7.5 (old, I know). The image will launch on an older OpenStack deployment (running version "Havana") but not a newer OpenStack (running version "Newton"). Looking at cloud-init.log: on the newer cloud, cloud-init seems to be blocking the instance boot process. the last thing it does is finish the mode "init" (setting SSH configuration, host keys, authorized_keys, etc). it doe23:06
cmartit appears that the process has hung but I don't have a usable console or way to log in locally and check -- at the moment I can only inspect the filesystem of the failed instance. Looking for troubleshooting tips :)23:06

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