15:00:09 #startmeeting third-party 15:00:09 Meeting started Mon Jan 25 15:00:09 2016 UTC and is due to finish in 60 minutes. The chair is mmedvede. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:13 The meeting name has been set to 'third_party' 15:00:41 hi third-party CI folks. Anyone here for the meeting? 15:00:46 hi 15:00:52 hi 15:00:54 Hello 15:00:55 good morning 15:00:58 I am sitting in today for anteaya 15:01:33 hi all, good morning 15:02:14 I have no announcements to make. Anyone has a topic they would like to discuss? 15:02:57 Not sure what is normally done at these meetings. 15:03:25 this is my first meeting so don't know either 15:03:42 Swanson: normally we answer questions that anyone who is running third-party CI has, and helping with problems they have 15:03:48 cbader: ^ 15:03:52 usually people bring up issues they have or recently solved 15:04:05 I've been having trouble getting jenkins to log into newly created nodes. I can use the keys and whatnot by hand to log in but jenkins can't seem to do this. 15:04:09 Anyone seen that? 15:04:39 cbader, looks like your issue right? ^^ 15:04:40 You might want to try to add the private key instead of pointing it to the file 15:04:52 I saw something similar, re adding nodes to Jenkins solved it, I think 15:05:04 yes I have not figured out why it doesn't use the file yet. 15:05:25 I also use key directly, not pointing to file 15:05:50 we are using user/psw in our env 15:06:24 I am still having a issue with zuul not connecting to gerrit. it is complaining about credentials but I have verified the private/public key and user. 15:06:39 Do you have that happening automagically on the node creation? Cause once the node is recreated I have to go back in and do it again. 15:07:55 Are you going to Jenkins>Manage Credentials> Private Key (Enter directly) that was the only thing the worked for me. 15:08:19 cbader: trivial question: is this gerrit account enabled? 15:08:31 cbader: did you try start zuul in debug mode? 'su zuul; zuul-server -d'? 15:08:32 all: there's an etherpad now to try to track issues and experiences: https://etherpad.openstack.org/p/thirdpartyci 15:08:54 #link 3rd party ci - setup etherpad https://etherpad.openstack.org/p/thirdpartyci 15:09:03 cbader, If I did that it worked. When that node is blown up overnight I then have to do it again with the new node. 15:09:18 link is also saved here under "reference links" https://wiki.openstack.org/wiki/Meetings/ThirdParty#Reference_links 15:09:29 thats the 3rd party ci wiki homepage ^^ 15:10:44 Swanson, so you did that and it only works when you manually register a jenkins slave with a jenkins amster? 15:10:50 I will look for my issue there thanks 15:11:48 asselin__, Mostly. Sometimes adding a key into jenkins doesn't work either. 15:12:03 asselin__, but I haven't looked into what was up with that too closely. 15:13:03 Swanson, just note that puppet probably removes the key and restores the link to the private key filename... 15:13:35 Swanson, http://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/templates/be.certipost.hudson.plugin.SCPRepositoryPublisher.xml.erb#n10 15:13:54 actually....that's for scp.... 15:14:34 asselin__, And certainly when the node is replaced what I did for the previous node is irrelevant 15:14:46 VPN she be a harsh mistress today. 15:15:40 Swanson, so you have secured jenkins? 15:15:50 Swanson: and your nodes, nodepool does update them daily? 15:17:14 asselin__, I have not secured jenkins. Wide open. Should I? 15:17:33 mmedvede, nodepool updates them daily. 15:17:35 Swanson, no...it should be optional.... 15:20:32 anything else on this topic? 15:21:11 I'll add this to the thirdpartyci document once it chooses to load. 15:21:25 I think it had already been listed. 15:21:32 So looks like pip 8.0.2 is out are people using it did it fix the issues from last week? 15:23:35 cbader: can you refresh us on the issues from last week? 15:24:12 We have not seen any troubles in our CI 15:24:50 there were issues with argparse was causing issues with modules not being able to load because it pip couldn't read what the requirements were needed. 15:26:02 I was creating a new Common-CI and ran into this issues so pinned mine to 7.1.2 to continue. 15:26:36 cbader: what version were you using before? 15:28:01 lennyb, It was a new install so I got what it pulled. Which was 8.0.0 so with what was being talked about I backed up to the last working version 7.1.2 and my issue went away. 15:31:05 In this meeting lull I would just like to throw out there my apologies to the world for my rouge ci spamming last week. At least I caught it quickly. 15:33:37 Swanson: I am interested to hear what caused it. That is my biggest fear :) 15:34:25 I screwed up and swapped out my small list of jenkins jobs for what I assume is the gigantic list of Infras jenkins jobs. 15:35:42 "I don't remember this file being this big... Sure am getting a lot of email..." 15:36:20 haha, that would do it 15:37:21 I guess you caught it fast, because I did not see any email on -dev or -infra lists about it 15:38:20 Swanson: thank you for sharing 15:38:40 mmedvede, I happy to serve as a warning to others. 15:39:15 Swanson, sorry...I didn't catch what was the root cause 15:40:20 asselin__, Updating some of my local project config files I managed to overwrite some files I didn't want to overwrite. (jenkins jobs for one) So be careful and double check your commits before starting up your cI. 15:41:12 Swanson, which files exactly? 15:42:28 asselin__, projects.yaml, I believe. 15:43:00 hmmm....I don't know why any change to that would cause out of control comments.... 15:43:12 Swanson: oh, I assumed it was zuul config 15:43:23 Swanson, do you have tox in your project-config repo? 15:43:33 not sure how changes just to jenkins config would make your CI spam 15:43:35 asselin__, I overwrote it with infra's. 15:44:21 Swanson: do you use zuul, or jenkins gerrit plugin? 15:44:39 I'm sorry. I also overwrote zuul's layout.yaml 15:45:02 I did both. I caught jobs and then got nailed by zuul. Same reason for both. 15:46:14 Updating elements and scripts and whatnot I ended up updating everything. 15:47:09 ok I see...you were re-syncing your project config nodepool files with upstreams project-config and copied more files than you intended 15:47:51 asselin__, That would be it exactly and with the clarity I should have provided in the first place. 15:48:05 ok :) 15:48:40 so perhaps a warning would be helpful? 15:50:09 It wouldn't hurt. The thing is when you're doing things fast and irritated things like this happen. A reminder that you could be yelled at by anteaya (sp?) wouldn't hurt. 15:53:39 fair warning on zuul config might be good 15:53:47 anything else? 15:55:15 let's get a few minutes back then 15:55:19 good discussion today, thank you everyone 15:55:24 Thanks 15:55:29 thanks 15:55:44 #endmeeting