[01:58] <blackboxsw> larsks: a volley of comments for you on Why bother with the split
[01:59] <blackboxsw> oops on https://code.launchpad.net/~larsks/cloud-init/+git/cloud-init/+merge/345113 rather
[17:18] <blackboxsw> This can land. thank you https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/343738
[17:32]  * blackboxsw kicked off an ec2-integration-x test run on the commandline (not in jenkins). So please don't kick that job in the UI
[17:49] <smoser> done
[17:54] <robjo> blackboxsw: noLnxDistro back in your court
[18:03] <blackboxsw> powersj: can you glance at my review today https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/342010
[18:03] <blackboxsw> robjo: thanks
[18:04] <powersj> blackboxsw: yeah
[18:05] <smoser> robjo: general opensuse question
[18:05] <smoser> there is a python-jsonpatch that is zypper installable . that is python2.7
[18:05] <smoser> but zypper search jsonpatch does not show a python3 version
[18:05] <smoser> is that expected?
[18:06] <robjo> that depends on the repositories enabled and the distribution
[18:06] <smoser> well, opensuse 42.3
[18:06] <robjo> if the devel:languages:python repo is anebaled python3-jsonpatch would show up or if the distribution is Tumbleweed
[18:06] <smoser> and i've not enabled new repositories as doing so would require me to bother you with that question
[18:07] <robjo> openSUSE 42.3 is using Python 2 by default and not many python3 packages are included by default
[18:07] <robjo> openSUSE Leap 15 will have mostly python3 packages as it is by default Python3 based
[18:07] <smoser> ok. so.. stick with python2 for the moment on suse
[18:08] <smoser> er... opensuse 42
[18:08] <smoser> right?
[18:08] <robjo> Leap 15 is expected in June sometime
[18:08] <smoser> k
[18:08] <robjo> yes python 2 on Leap42.x
[18:11] <smoser> robjo: ok. in a container i did recraet a failure of nose
[18:11] <smoser> but not the one you saw
[18:13] <robjo> hmm inconsistencies :( , the failure I saw was produced on an openSUSE Tumbleweed box with tox -e py3
[18:14] <robjo> because I have a mix of Python2 and Python 3 on my Leap 42.3 box I cannot test there
[21:43] <smoser> robjo: with https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/345630 i can run
[21:43] <smoser> python -m nose tests/unittests cloudinit/
[21:43] <smoser> on opensuse 42.3
[21:44] <smoser> err.. hmm. i thought i could.
[21:47] <smoser> err maybe not. that does fix just running that test case file, but running them all i get
[21:47] <smoser> http://paste.ubuntu.com/p/YGkb42wvzp/
[21:47] <smoser> i'll look more tomorrow
[21:48] <smoser> powersj, blackboxsw https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/345627
[21:48] <smoser> that is what is allowing me to somewhat sanely get a opensuse environment
[21:48] <smoser> ./tools/run-container --keep opensuse/42.3
[21:49] <robjo> I wonder what would trigger the insertion of "'http://ubuntu-mirror.suse.de/ubuntu' in my case
[21:49] <robjo> that looks almost like the test is using the domain name of the test machine and thus the test itself would be host dependent
[21:50] <robjo> I'll try and find some time to look into this tomorrow, have to get some docs into a state where they can be reviewed first
[21:51] <smoser> no. that is doc'd in cloudinit/config/cc_apt_configure.py
[21:51] <smoser> it looks for <distro>-mirror
[21:52] <smoser> i'll get the tests sorted in run-container for opensuse 42.3 tomorrow.
[21:52] <smoser> i have to leave "right now"
[21:52] <smoser> later
[21:52] <robjo> but in the test it shouldn't, or the "expected" resuts cannot be matched
[23:45] <ecksit> howdy! i'm doing some user and group management using the cloud-init module that dynamic writes the file. is there a way i can set the `sudo` value to something that won't trigger the sudoers file to be created? (worth noting i haven't been able to try this on an image just yet)
[23:46] <ecksit> something like `sudo: false` would be perfect but i cannot locate it in the git repository