[01:39] <ckonstanski> Trying to bust out the two easy issues now. I created a launchpad bug for the rc-service one. How do I assign it to myself? Or do I not do that? (This is where I learn the procedures around launchpad)
[01:54] <ckonstanski> Pushed commits for issues 1727121 and 1727126
[01:55] <ckonstanski> A brreakdown in the "hacking" instrucitons. Will catch up tomorrow.
[02:31] <prometheanfire> cool
[02:31] <prometheanfire> I made https://code.launchpad.net/~prometheanfire/cloud-init/+git/cloud-init/+merge/332754 , but I'd rather just use yours
[02:34] <prometheanfire> ckonstanski: all you should need to do is go to your fork/branch and click the merge this button
[03:18] <ckonstanski> target reference path? master?
[03:20] <ckonstanski> found it in "hacking" -- master
[03:21] <ckonstanski> done
[12:14] <prometheanfire> ckonstanski: cool, link?
[14:32] <ckonstanski> http://cloudinit.readthedocs.io/en/latest/topics/hacking.html
[14:51] <prometheanfire> ckonstanski: sorry, to your merge request :P
[14:54] <ckonstanski> https://code.launchpad.net/~ckonstanski/cloud-init/+git/cloud-init/+merge/332755
[14:54] <ckonstanski> https://code.launchpad.net/~ckonstanski/cloud-init/+git/cloud-init/+merge/332756
[14:54] <ckonstanski> 2 different ones
[15:14] <smoser> ckonstanski: prometheanfire i've seen your bugs and mp... i do want to review for you.
[15:14] <smoser> just time and such. but we'll try to get some feedback today.
[15:18] <prometheanfire> smoser: sure, don't need to do mine, do ckonstanski's
[15:46] <prometheanfire> removed (deleted)
[16:07] <powersj> smoser: your update looks good, however I am unsure about the variable substitution into the shell script
[16:08] <powersj> when it generates the xml right now it produces "release={release}
[16:08] <powersj> triggerwhat={triggerwhat}"
[16:08] <powersj> which isn't what we want I think
[16:08] <smoser> hm..
[16:09] <smoser> powersj: i was trying ot generate the xml locally
[16:09] <powersj> This is why there was lots of copy and pasting... I always got frustrated with this
[16:09] <smoser> but dont know how ?
[16:09] <smoser> if i run './test-jenkins-jobs' locally, it ends up i think trying to post xml
[16:09] <smoser> (and failing reasonably)
[16:09] <powersj> the test-jenkins-jobs will run "jenkins-jobs test <dir>"
[16:10] <smoser> yeah, but lcoally
[16:10] <powersj> and if it produces XML without any exception, then it means the job at least generated
[16:10] <powersj> that is all local
[16:10] <powersj> won't try to push anything or update the jenkins as there are no creds in that repo :)
[16:10] <smoser> http://paste.ubuntu.com/25817851/
[16:11] <smoser> that is on master (with jenkins-jobs installed from archive)
[16:11] <powersj> what is your version of jenkins-job-builder? because I am using pipelines it has to be a certain version
[16:11] <powersj> yeah the archive version won't work
[16:12] <powersj> if you look at the readme or travis file you will see I have ot use: jenkins-job-builder==2.0.0.0b2
[16:18] <smoser> powersj: pip install jenkins-job-builder just got me 1.6.2
[16:18] <ckonstanski> ckonstanski@sphinkpad:~/jobs/talligent/projects/openbook-v4-ci/jjb $ cat requirements.txt
[16:18] <ckonstanski> jenkins-job-builder>=2.0.0.0b2
[16:18] <ckonstanski>  
[16:18] <ckonstanski> That'll git er
[16:19] <powersj> smoser: yeah if you add the >= or == with version it'll do it
[16:31] <smoser> powersj: :-(
[16:31] <smoser> why is my macro not expanding
[16:40] <smoser> powersj: http://paste.ubuntu.com/25817997/
[16:40] <smoser> "yaml is hard"
[16:41] <powersj> HAHAHAHA
[16:41] <smoser> started with 'foo.yaml' like rthis
[16:41] <smoser>  http://paste.ubuntu.com/25818005/
[16:41] <smoser> and iterated
[16:43] <powersj> that looks good
[16:43] <smoser> powersj: i'm not sure if i have the 'artifacts' right though
[16:43] <smoser> what adds the 'cloud-init/' that you have in cloud-init/integration.yaml
[16:43] <smoser>       - archive:
[16:43] <smoser>           artifacts: 'cloud-init/results/**'
[16:43] <powersj> the git clone
[16:44] <powersj> clone's into cloud-init
[16:44] <smoser> got it. thanks.
[16:44] <powersj> so $WORKSPACE/cloud-init
[16:52] <powersj> smoser: any reason to not merge?
[16:52] <powersj> looks good on my end
[16:53] <smoser> powersj: go for it.
[16:54] <ckonstanski> Is cloud-init an openstack project? Need to know for a question asked at work.
[17:01] <powersj> ckonstanski: we are not, smoser could give better history though
[17:01] <powersj> smoser: jobs deployed, looks good! thank you :D
[17:03] <smoser> ckonstanski: cloud-init 2.0 kind of started as a openstack project, but that work was shelved, to rather continue development on 1.0
[17:27] <smoser> powersj: i'm going to hit 'build-now'
[17:28] <smoser>  https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-integration-proposed-x/
[17:28] <powersj> smoser: go for it
[17:29] <prometheanfire> ckonstanski: it's not, just heavilly used by images running on openstack
[17:47] <smoser> powersj: https://jenkins.ubuntu.com/server/view/cloud-init/job/cloud-init-integration-proposed-x/80/console :-(
[17:47] <powersj> AssertionError: '0.cloud-init.mypool' not found in ''
[17:47] <powersj> FAIL: test_ntpq_servers (tests.cloud_tests.testcases.modules.ntp_pools.TestNtpPools)
[17:47] <smoser> ugh. how the $*(# did that fail
[17:47] <powersj> love this new output btw... thanks :)
[17:48] <smoser> while 79 passed
[17:48] <powersj> modules/ntp_pools
[17:49] <powersj> uhh hold on
[17:49] <powersj> it built the deb....
[17:49] <powersj> something may have changed when I merged your jenkins job... doesn't look like it is doing the pull-lp-source cloud-init xenial-proposed
[17:50] <smoser> oh? did i foobar that ?
[17:50] <powersj> oh your builder is wrong
[17:50] <powersj> review fail on my part
[17:50] <powersj> see I trust you too much ;)
[17:50] <smoser> i grabbed the wrong code block
[17:50] <smoser> phft
[18:00] <smoser> powersj: mp coming . sorry.
[18:00] <powersj> no worries, I feel bad for missing it in the review
[18:11] <smoser> powersj: the start dir of a job
[18:11] <smoser> isnt it going to be the work dir ?
[18:11] <smoser> ie, a base, clean dir ?
[18:13] <powersj> smoser: I don't believe so
[18:13] <powersj> that's why I have rm everywhere
[18:13] <smoser> doesnt taht seem scary and silly ?
[18:13] <smoser> ie, what would be in a directory if it was not empty ?
[18:13] <smoser> only another jobs data
[18:14] <smoser> which we are going to remove ?
[18:14] <powersj> it is scary :)
[18:14] <powersj> hence the rm -rf *
[18:15] <smoser> https://stackoverflow.com/questions/24412418/whats-the-working-directory-in-jenkins-after-executing-a-shell-command-box
[18:15] <smoser> Building remotely on torkoal (metal-amd64) in workspace /var/lib/jenkins/slaves/torkoal/workspace/cloud-init-integration-proposed-x
[18:17] <smoser> doesnt it seem completely broken ?
[18:21] <powersj> that seems to be talking about multiple build steps, which may treat it differently I haven't played with that though
[18:23] <powersj> hence why folks ask about cleaning up the workspace: https://stackoverflow.com/questions/28683914/is-there-any-way-to-cleanup-jenkins-workspace
[18:24] <smoser> powersj do you get hwat i'm saying ?
[18:24] <smoser> ah. ok. i get it.
[18:24] <powersj> I do, but I'm not sure if you are implying that Jenkins should be cleaning it up for us and we should not be doing the rm or something else
[18:24] <smoser> you can't run a job twice at the same time.
[18:25] <powersj> that is correct
[18:25] <smoser> ok.
[18:32] <smoser> powersj: https://github.com/canonical-server/jenkins-jobs/pull/15
[18:34] <powersj> smoser: I like what you did there
[18:37] <smoser> powersj: how quick does it go live ?
[18:37] <powersj> smoser: it is live now
[18:38] <powersj> smoser: update jobs every 15mins, I just kicked it though to get it live
[18:41] <smoser> k
[18:41]  * smoser build-nows
[18:42] <smoser> oh fudge
[18:44] <smoser> :-( https://github.com/canonical-server/jenkins-jobs/pull/16
[18:49] <powersj> smoser: accepted and jobs updated
[19:10] <powersj> smoser: all looks good now?
[19:10] <smoser> yeah. \o/
[19:10] <powersj> :)
[19:11] <smoser> now some day, clean  up all the other jobs.
[19:11] <smoser> x ran, i pushed 'go' on 'z'
[19:11] <powersj> yeah
[19:11] <smoser> and then will do on 'a'
[19:11]  * smoser will try to script somthing like i suggested to grab results and put them on a bug.\
[19:11] <smoser> blackboxsw: ^
[19:12] <smoser> blackboxsw: did you manually do all those bug updates ?
[19:12] <blackboxsw> smoser: yeah I'm wrapping up each test (I was missing some it looked like)
[19:12] <blackboxsw> jsonschema warning->debug is last
[19:12] <blackboxsw> then I think we are good
[19:12] <blackboxsw> lemme push
[19:13] <blackboxsw> I manually added SRU verification logs to our existing ubuntu-sru/bugs*
[19:14] <blackboxsw> smoser: pushed b0b83fc0e659f3e30f948ef0b9a63df14054aca8 to ubuntu-sru
[19:15] <blackboxsw> I've manually separated the verification results content and added it to the bug as I've untagged the verification-needed ->done switches
[19:16] <blackboxsw> but left the script/results as one file in ubuntu-sru
[19:16] <blackboxsw> we could separate easily if you wanted so it's easier to add results to bugs as a comment
[19:18] <blackboxsw> last one to validate here http://pad.lv/#1724354
[19:20] <smoser> blackboxsw: i'm pretty sure you can do this:
[19:20] <smoser>  http://paste.ubuntu.com/25818813/
[19:22] <blackboxsw> +1 smoser
[20:09] <blackboxsw> ok pushed and included ryan's sru info for https://launchpadlibrarian.net/341226002/1718287.log
[20:25] <smoser> blackboxsw: fyi https://bugs.launchpad.net/cloud-init/+bug/1727358
[20:25] <ubot5> Ubuntu bug 1727358 in cloud-init (Ubuntu) "cloud-init is slow to complete init on minimized images" [Undecided,Incomplete]
[20:27] <blackboxsw> hrm from sru validation run on 17.1?
[20:27] <smoser> no.
[20:28] <smoser> from cyphermox reported yesterday.
[20:28] <smoser> i have to run :-(
[20:28] <powersj> should get actual cloud-init analyze output
[20:28] <smoser> it wont help much
[20:28] <smoser> the 120 seconds is lost in that one line of debug
[20:28] <powersj> ah
[20:28] <powersj> so he already did the analyze part ;)
[20:28] <smoser> i have to run, we have successful integration-proposed-x z a
[20:29] <powersj> woohoo
[20:29] <smoser> well, i did
[20:29]  * powersj should now go read it
[20:29] <smoser> so we should copy those and attach to the sru bug
[20:29] <smoser> i can do that later, but have to run now.
[20:36] <roadmr> hey folks
[20:39] <roadmr> cloud-init 0.7.5 on ubuntu 14.04 doesn't understand the apt: proxy: value, instead it wants apt_proxy. I asked for help with lxc and they told me to report this for cloud-init. I can file a Launchpad bug if you like.
[20:39] <roadmr> https://github.com/lxc/lxd/issues/3975
[20:54] <dpb1> roadmr: file a bug please
[20:55] <roadmr> dpb1: will do!
[20:55] <roadmr> dpb1: https://bugs.launchpad.net/cloud-init, right?
[20:55] <blackboxsw> yeah hrm roadmr I think it's worth a bug, I'm not sure if cloud-init 17.1 would support the same cloud-config keys back in 0.7.5 but it's worth a bug so we discuss and document whether or not we'll backport that cloud-config
[20:55] <blackboxsw> yeah roadmr
[20:55] <blackboxsw> https://bugs.launchpad.net/cloud-init/+filebug
[20:55] <dpb1> blackboxsw: right, we will want to make our stance clear in the bug either way
[21:06] <roadmr> https://bugs.launchpad.net/cloud-init/+bug/1727527
[21:06] <ubot5> Ubuntu bug 1727527 in cloud-init "cloud-init 0.7.5 doesn't honor the apt: proxy: setting, needs apt_proxy instead" [Undecided,New]
[21:06] <roadmr> the alternate solution works fwiw, so it doesn't seem horrible, but it would be nice if it were documented :)
[21:07] <blackboxsw> thanks for the bug
[21:14] <roadmr> np :)