Tuesday, 2017-10-17

mnaserShrews things should be okay now00:47
mnaserfun ops graphs - https://i.imgur.com/0LSHHb1.png - router psu deteriorating till failure (but still managed to get enough voltage to report SNMP)00:47
*** jkilpatr_ has quit IRC01:37
*** zhuli has quit IRC02:22
*** zhuli has joined #zuul02:22
dmsimardwhat, obscure scenarios ? We think about those first !02:27
dmsimardjeblair: for all the negative press zuul v3 gets, we should pin those positive "testimonials" somewhere :p02:27
*** jhesketh has quit IRC02:35
mrhillsmanagreed02:36
*** cinerama has quit IRC02:36
mrhillsmancoming in not know anything it is not too bad of a task to get somewhat up to speed and get things working02:37
*** jhesketh has joined #zuul02:38
*** cinerama has joined #zuul02:41
*** bhavik1 has joined #zuul03:54
*** bhavik1 has quit IRC04:13
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: web: make console-stream tenant scoped  https://review.openstack.org/50545205:08
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: web: add /{source}/{project}.pub route  https://review.openstack.org/50253005:08
tobiashtristanC: I just hit the rebase button so your stack is linear and I can put something on top of it05:09
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: web: add /tenants route  https://review.openstack.org/50326805:18
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: web: add /{tenant}/status route  https://review.openstack.org/50326905:18
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: web: add /{tenant}/jobs route  https://review.openstack.org/50327005:18
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: web: add /{tenant}/builds route  https://review.openstack.org/46656105:18
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: web: make console-stream tenant scoped  https://review.openstack.org/50545205:18
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: web: add /{source}/{project}.pub route  https://review.openstack.org/50253005:18
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Adapt relative streaming urls to tenant scope  https://review.openstack.org/51248305:18
tobiashtristanC: ^ had to rebase your whole stack due to merge conflict (and added a change on top), hope that's ok for you05:19
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Adapt relative streaming urls to tenant scope  https://review.openstack.org/51248305:46
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Add support for result data in child jobs  https://review.openstack.org/50480806:21
tobiashjeblair: fixed your result data change ^06:22
*** hashar has joined #zuul07:53
*** electrofelix has joined #zuul08:51
*** sambetts|afk is now known as sambetts09:20
*** smyers has quit IRC09:54
*** smyers has joined #zuul09:56
*** openstackgerrit has quit IRC10:33
*** hashar has quit IRC10:33
*** openstackgerrit has joined #zuul10:57
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Handle tox environments via tox config  https://review.openstack.org/51244810:57
*** jkilpatr has joined #zuul11:06
*** zhuli has quit IRC11:11
*** zhuli has joined #zuul11:12
odyssey4meso, giving some thought to using zuul for ansible role/playbook testing a question has come up11:12
*** zhuli has quit IRC11:12
odyssey4meif a role/playbook is written with one version of ansible in mind, and zuul has some unknown version of ansible - how do we make them all get along?11:12
*** zhuli has joined #zuul11:12
odyssey4meansible versions are quite different, and at this stage I can see us having a rough time trying to use zuul's ansible to run any of our roles consistently forever, as we have per branch ansible version support11:14
*** jkilpatr has quit IRC11:27
*** jkilpatr has joined #zuul11:27
Shrewsmnaser: yes, seems to be doing much better since last night. thanks.12:01
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Harden exception handling around instance deletes  https://review.openstack.org/51241312:31
dmsimardodyssey4me: It's something I have thought about as well, the obvious workaround is to install and run ansible within your job but there would be great benefits to running "natively". The thing is Zuul (executor) itself has a significant amount of Ansible code (plugins, modules, callbacks) which makes it hard to support different versions simultaneously.12:43
dmsimardI don't think we expose the ansible version in zuul other than in the ara report right now, maybe putting a bit more visibility on it could be a first step12:47
*** dkranz has joined #zuul12:49
*** pabelanger has quit IRC13:01
*** pabelanger has joined #zuul13:01
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: WIP: Migrate legacy jobs  https://review.openstack.org/51261113:11
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: WIP: Migrate legacy jobs  https://review.openstack.org/51261113:15
Shrewsjeblair: mordred: I'm a bit confused on what to do with the nodepool jobs (e.g. ^^^) since we intend to merge the features branch back into master at some point. Should I duplicate some of the work from 512611 into both branches? Or maybe we should go ahead with the merge and get rid of the feature branch?13:33
mordredShrews: that's a great question13:36
pabelanger+1 for merge to master. will make rolling out new builders a little easier too13:37
mordredShrews: btw - if you feel like playing - there's a new shiny devstack base job - https://review.openstack.org/#/c/500365/29/.zuul.yaml examples of use there <--13:37
Shrewsmordred: ++13:38
mordredShrews: however - you can define all of the jobs in master and just have a project: stanze .zuul.yaml in the feature branch that uses them13:38
mordredShrews: so maybe it's a good opportunity to play with that even though it's not STRICTLY necessary - you know, since we've got a good opportunity to flesh out bugs and whatnot13:39
Shrewsmordred: wouldn't that make the merge back to master more difficult?13:39
mordredShrews: btw -im rechecking that shade change13:39
mordredShrews: nah - we can always null-merge the .zuul.yaml file13:40
Shrewsmordred: i sort of feel like it's time we did the merge anyway. if we do that, i could just change master. but i'll defer to the actual person(s) doing the merge13:41
mordredShrews: I'm game to merge nodepool feature back to master myself - but I think we need to make sure folks using puppet-openstackci aren't going to all of a suden get upgraded13:42
tobiashnodepoolv3 is incompatible to zuulv2 so shouldn't we merge zuul and nodepool to master at the same time?13:48
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Handle tox environments via tox config  https://review.openstack.org/51244813:56
openstackgerritTobias Henkel proposed openstack-infra/zuul feature/zuulv3: Make executor hostname configurable  https://review.openstack.org/51262913:57
mordredtobiash: yah - that's my main reason to be hesitant13:58
Shrewsmordred: i suppose i could move that job migration change to master, and just remove the .zuul.yaml from features/zuulv3 and that should work, yeah?14:06
Shrewsgoing to try that and find out14:10
mordredShrews: sort of ... you still need a .zuul.yaml in feature/zuulv3 that lists the jobs to run - jobs in the master branch get an implied branch matcher ...14:15
mordredShrews: I think jeblair wrote an updated piece of doc about this yesterday ...14:15
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Migrate legacy jobs  https://review.openstack.org/51263714:15
mordredShrews: https://docs.openstack.org/infra/manual/zuulv3.html#stable-branches14:16
mordredShrews: it's written about stable branches - but it holds for all branches14:16
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Update bindep role defaults to be more sane  https://review.openstack.org/51263914:18
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Migrate legacy jobs  https://review.openstack.org/51263714:19
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Update jobs for features/zuulv3 branch  https://review.openstack.org/51264214:22
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Migrate legacy jobs  https://review.openstack.org/51263714:28
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Update jobs for features/zuulv3 branch  https://review.openstack.org/51264214:29
Shrewssorry for the noise. trying some stuff  :/14:29
openstackgerritMerged openstack-infra/zuul-sphinx master: Add support for project-templates  https://review.openstack.org/51244914:36
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Update jobs for features/zuulv3 branch  https://review.openstack.org/51264214:36
mnaserawesome work jeblair ... changes to zuul yaml are *so* fast :)14:54
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Update jobs for features/zuulv3 branch  https://review.openstack.org/51264214:54
openstackgerritMerged openstack-infra/zuul feature/zuulv3: New client command for printing autohold requests  https://review.openstack.org/51236014:54
mnasermoving jobs to non voting without infra, yay for successful use cases14:55
pabelanger+114:55
pabelangerI think it is awesome that a non infra person wrote a publisher to docker, all in repo, and got it working14:56
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Migrate legacy jobs  https://review.openstack.org/51263714:56
pabelangerwithout having to land code in project-config14:56
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Migrate legacy jobs  https://review.openstack.org/51263714:59
jlkpabelanger: can you explain why https://review.openstack.org/#/c/512458/ was made?15:18
pabelangerjlk: to workaround that we don't have access to ansible facts on executors15:19
pabelangerso ansible_user_dir is undefined15:19
jlkah, that wasn't clear from the commit message15:20
pabelangerjlk: yah, it merged before I could update it per your comment15:20
jlkgotcha15:21
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Update jobs for features/zuulv3 branch  https://review.openstack.org/51264215:27
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Harden exception handling around instance deletes  https://review.openstack.org/51241315:38
Shrewscool. pabelanger, we should probably restart launchers when convenient to get that ^^^. i don't think there's a huge hurry though15:41
pabelangerwfm15:43
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Several executor threading fixes  https://review.openstack.org/51267315:45
*** sambetts is now known as sambetts|afk16:26
openstackgerritJeremy Stanley proposed openstack-infra/zuul feature/zuulv3: Periodic refname, newrev and oldrev legacy vars  https://review.openstack.org/51270116:30
*** bhavik1 has joined #zuul16:31
*** bhavik1 has quit IRC16:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Several executor threading fixes  https://review.openstack.org/51267316:49
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Don't return POST_FAILURE when aborting post playbooks  https://review.openstack.org/51271216:49
dmsimardjeblair, mordred: odyssey4me had an interesting question earlier this morning that I also wonder about: http://eavesdrop.openstack.org/irclogs/%23zuul/%23zuul.2017-10-17.log.html#t2017-10-17T11:12:1217:01
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Don't return POST_FAILURE when aborting post playbooks  https://review.openstack.org/51271217:01
jeblairclarkb, tobiash: ^17:01
clarkbty17:01
tobiashlgtm17:03
jeblairdmsimard, odyssey4me: yes, mordred and i were talking about this recently too.  i think we would like to support that better.  at the moment, that would probably mean that we would take on more work to support more versions of ansible simultaneously.  it may be feasible, but not something to promise lightly.  probably something to discuss in the coming weeks.17:04
jeblairShrews: ^17:04
odyssey4meja17:04
dmsimardyeah, I think we want to support that, the question is more how to do it17:05
dmsimardi.e, install ansible (zuul-executor ?) *inside* the bubblewrap at a specified version ? something else ?17:06
dmsimard¯\_(ツ)_/¯17:06
jeblairyeah, there are questions about installation, our plugins, and executor behavior17:06
dmsimardMaintaining the Ansible code we have in Zuul to work across different versions of Ansible is definitely challenging to say the least. Just for ARA, which pulls a much smaller surface, is not trivial17:07
dmsimardI end up having to maintain differences between 2.2, 2.3 and 2.4 right now and I already can't wait until 2.4 is EOL already to do things differently with what's coming in 2.517:08
jeblairdmsimard: yes, though hopefully minor release upgrades would be less work...17:08
jeblairoh here's a question17:08
dmsimardansible doesn't follow semver17:08
dmsimard2.3 to 2.4 doesn't guarantee you anything17:08
dmsimard2.3.0 to 2.3.1, is probably fine17:08
jeblairodyssey4me: do you need, say, multiple 2.3 releases (ie, 2.3.1, 2.3.2), or would "latest 2.3" and "latest 2.4" be sufficient?17:09
dmsimardTypically (as an ansible end user), it's based on major releases like 2.3 and 2.4. Dot releases are usually backwards compat bug fixes.17:10
jeblairdmsimard: for a fun 2.3 -> 2.4 executor behavior change, see this, which i wrote yesterday: http://git.openstack.org/cgit/openstack-infra/zuul/tree/zuul/executor/server.py?h=feature/zuulv3#n140617:10
dmsimardjeblair: oh, it's much more ugly for ara: https://github.com/openstack/ara/blob/master/ara/config.py#L26-L10017:11
mordredyah - this is an area I totally want to support more better - but also - WOW17:11
mordredthat said - hopefully starting with 2.4 -> 2.5 we can provide some feedback on whether or not changes might break things ...17:12
pabelangeryah, once we start reporting against ansible/ansible, our unit testing for zuul should start to expose issues17:13
pabelangerthen we just import unit testing with more coverage17:13
odyssey4mejeblair we're typically testing against the latest of a minor, so 2.4.x/2.3.x - we need to use it outside of infra, so we'd need a constraints file to reference on a sha as the 'reference' version that was tested17:14
*** weshay|ruck is now known as weshay|afk_see_r17:14
odyssey4meyeah, minor revs for ansible are bad when it comes to underlying changes, and often breaking behaviour17:15
odyssey4meas they add more tests for things they never knew existed it's getting better though17:15
dmsimardoh yeah, sometimes it's not "regressions", it's "fixing unintended usage" or stuff like that :)17:23
jlkthose are features, they're bugs.17:27
openstackgerritJeremy Stanley proposed openstack-infra/zuul feature/zuulv3: Be explicit about legacy var additions/omissions  https://review.openstack.org/51276918:02
kklimondahow will zuul-executor behave if gearman connection is lost while it's executing a job? Will it keep trying to report it back, or just drop it?18:17
openstackgerritJeremy Stanley proposed openstack-infra/zuul feature/zuulv3: Be explicit about legacy var additions/omissions  https://review.openstack.org/51276918:29
fungikklimonda: i believe we (somewhat recently) fixed it so that the scheduler will reschedule builds from an executor which disconnects, but i don't know what the executor will do after that (pretty sure it won't be able to get the obsoleted builds reported back to gerrit in the end at least)18:31
fungikklimonda: that was mostly in the interest of making hard/unanticipated shutdown of executors less disruptive to end users18:32
pabelangerI think executors just pass results down into python-gear and that is about it18:33
kklimondafungi: is there a timeout before scheduler marks executor as down, or does it do it as soon as it gets to it?18:34
* fungi finds the change18:36
fungihttps://review.openstack.org/510223 Always retry jobs on executor disconnect18:37
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Several executor threading fixes  https://review.openstack.org/51267318:37
fungikklimonda: so it's if gear reports DISCONNECT as the result, i think18:38
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Don't return POST_FAILURE when aborting post playbooks  https://review.openstack.org/51271218:39
*** electrofelix has quit IRC18:39
kklimondamhm, thanks - we've been having some network issues recently, and it seems zuulv3 is not going to magically fix those ;)18:39
fungikklimonda: meaning it's less up to the zuul scheduler, more up to the gearman service it's relying on18:39
fungikklimonda: if you're having issues with connectivity between your control plane services (e.g. executor to gearman or in v2 launcher/jenkins master to gearman) then i don't expect v3 will necessarily make things any more robust there18:41
pabelangerfungi: right, but I think when we move to zookeeper, we'll have a little more robustness? If I understand how locks are working with nodepool nodes18:42
fungiyeah, once we can replace gearman in that part of the architecture, perhaps18:43
fungibut that's not v3 as it exists today/for release18:43
pabelangeryah18:44
fungimore of a 3.x or 4.018:44
pabelangerzuulv4, hype!18:44
tristanCtobiash: no worries, thanks for the rebase. I'll be afk for a couple more week19:30
tobiashtristanC: my deployment now includes your stack and it looks great :)19:32
tristanCtobiash: nice! does the zuul-web randomly return 500s or is it consistent?19:34
dmsimarda wild tristanC has appeared ! Hi :D19:34
tristanCi mean, on the status page or the builds list, the controllers sometime fail for no reason19:34
tristanCdmsimard: hello :-)19:35
tobiashtristanC: didn't notice 500s so far19:35
tristanCgreat, then I suspect an incorrect aiohttp version or something on my side19:36
tobiashtristanC: have it working since today, but I'll observe this19:37
*** weshay|afk_see_r is now known as weshay|ruck19:42
tristanCtobiash: thanks, the code in await blocks may need a try/except since there was no traceback/error message in logs19:46
tristanCi'll have a fresh look in 2 weeks19:47
tobiashk, will check this if I notice 500s19:48
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Migrate legacy jobs  https://review.openstack.org/51263719:51
*** dkranz has quit IRC19:56
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Migrate legacy jobs  https://review.openstack.org/51263719:59
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Migrate legacy jobs  https://review.openstack.org/51263720:01
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Migrate legacy jobs  https://review.openstack.org/51263720:03
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Migrate legacy jobs  https://review.openstack.org/51263720:21
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Migrate legacy jobs  https://review.openstack.org/51263720:36
dmsimardmordred: just noticed something in zuul_stream for action plugins: http://logs.openstack.org/54/509254/4/infra-check/zuul-stream-functional/8ae19d1/stream-files/stream-job-output.txt20:38
dmsimardsearch for "2017-10-04 13:04:44.434081 | TASK [Output a debug sentence]"20:38
dmsimardNotice how the action plugin (debug) runs on both nodes and they are not prefixed by the node ?20:39
dmsimardI'll try and hunt that down, found it while looking for another bug :/20:40
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Migrate legacy jobs  https://review.openstack.org/51263720:47
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool master: Migrate legacy jobs  https://review.openstack.org/51263720:49
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Update jobs for features/zuulv3 branch  https://review.openstack.org/51264220:51
openstackgerritJames E. Blair proposed openstack-infra/zuul-jobs master: upload-pypi: make repository url optional  https://review.openstack.org/51286221:16
openstackgerritIan Wienand proposed openstack-infra/zuul feature/zuulv3: Add a projects_by_name view of zuul.projects  https://review.openstack.org/51286821:24
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Don't set the build result to ABORTED  https://review.openstack.org/51288322:14
openstackgerritMerged openstack-infra/zuul-jobs master: upload-pypi: make repository url optional  https://review.openstack.org/51286222:27
openstackgerritMerged openstack-infra/zuul-jobs master: Update bindep role defaults to be more sane  https://review.openstack.org/51263923:15
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Don't set the build result to ABORTED  https://review.openstack.org/51288323:19

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