Thursday, 2017-02-09

*** herlo has quit IRC02:59
*** herlo has joined #zuul03:01
*** herlo has quit IRC03:01
*** herlo has joined #zuul03:01
*** saneax-_-|AFK is now known as saneax03:04
*** saneax is now known as saneax-_-|AFK03:32
*** Cibo_ has joined #zuul04:03
*** bhavik1 has joined #zuul04:41
*** bhavik1 has quit IRC04:49
*** saneax-_-|AFK is now known as saneax04:51
*** saneax is now known as saneax-_-|AFK05:16
*** saneax-_-|AFK is now known as saneax06:02
*** TheJulia_ has joined #zuul06:29
*** patrickeast_ has joined #zuul06:29
*** TheJulia has quit IRC06:33
*** patrickeast has quit IRC06:33
*** TheJulia_ is now known as TheJulia06:33
*** patrickeast_ is now known as patrickeast06:33
*** abregman has joined #zuul06:35
*** abregman has quit IRC09:01
*** Cibo_ has quit IRC09:02
*** openstackgerrit has quit IRC09:03
*** bhavik1 has joined #zuul09:11
*** bhavik1 has joined #zuul09:11
*** hashar has joined #zuul09:17
*** abregman has joined #zuul09:34
*** bhavik2 has joined #zuul10:06
*** bhavik1 has quit IRC10:08
*** bhavik2 has quit IRC10:11
*** Cibo_ has joined #zuul11:44
*** openstackgerrit has joined #zuul13:29
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: WIP: Implement node launching  https://review.openstack.org/43152313:29
Shrewsjeblair: 431523 is where I might need some guidance in using some fakes for the test_nodelaunchmanager tests13:30
mordredShrews: you ready for the game tonight?13:38
Shrewsmordred: oh? is there some sort of sportsball event occuring in this area tonight??? I hadn't heard13:39
* Shrews delets the snark and changes answer to "hell yes"13:40
mordred:)13:40
mordrednicely played13:40
Shrewsmordred: are we taking bets on which quarter Grayson trips someone?13:41
Shrewserr, half13:41
Shrewsi have to get out of football mode13:41
mordredShrews: it's the UNC game - the answer should be 'both' right?13:48
mordredShrews: jesusaur has some review comments for you on https://review.openstack.org/#/c/428428/ that you might otherwise miss13:55
mordredShrews: (I believe they can be handled in a follow up if they're valid)13:56
Shrewsmordred: yep. getting around to responding13:58
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Assign node set to node requests  https://review.openstack.org/42842813:59
mordredShrews: k. I just +2'd that stack14:01
jeblairthey are good comments, i'm glad i saw them14:03
jeblairShrews: i will pitch in on 523 after breakfast14:03
Shrewsmordred: jeblair: i think all of his concerns are already addressed, except for the min-ready one which I'm a bit unclear on. But none of that is implemented yet, anyway.14:04
openstackgerritMerged openstack-infra/nodepool master: Support AFS mirrors for nodepool diskimages  https://review.openstack.org/41427314:05
*** saneax is now known as saneax-_-|AFK14:12
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Remove 'template-' from image name format  https://review.openstack.org/43156414:13
Shrewspabelanger: mordred: ^^^ addresses the 'template' thing14:13
mordred++14:15
Shrewsjeblair: re: 523, i really need access to the config Provider object, the dict of config Label objects, and the ProviderManager to pass to the launch manager. I have yet to devine how to do that (though I've gotten distracted by other tasks since I submitted that).14:16
Shrewsmordred: lemme make another cup of coffee and i'll get to your shade reviews14:16
mordredmmm. coffee14:17
mordredI shall also drink another cup of coffee14:17
jeblairShrews: well, all of those things used to be in the main config object14:18
*** jlk has quit IRC14:22
openstackgerritMerged openstack-infra/zuul master: Fix setting of GIT_SSH for timer merge jobs  https://review.openstack.org/43087214:30
jeblairShrews: so i guess i'm not entirely sure what you're asking there or how i can help14:46
* Shrews context switches back14:46
Shrewsjeblair: how do i grab this "main config" object?14:47
jeblairShrews: there's a path from the main nodepool class through the request handler and nodelaunchmanager to the node launcher, right?14:47
Shrewsit looked like i'd have to poke into the builder or nodepool internals to get it14:47
openstackgerritMerged openstack-infra/zuul master: Set keepalives for gerrit connections  https://review.openstack.org/23898814:49
Shrewsjeblair: well, yeah. but in the test scenarios, I don't have all those things14:49
Shrewswhich is why i suggested the mocks, so i can simplify the test to only testing nodelaunchmanager14:49
jeblairShrews: ah, there's a useNodepool method that gets you a nodepool14:50
openstackgerritMonty Taylor proposed openstack-infra/zuul master: Put loggers into zuul namespace  https://review.openstack.org/43157914:50
jeblairthat's in the test_node_assignment test14:51
jeblairso it should be running a nodepool14:51
Shrewsjeblair: yeah. i was sort of hoping there was an existing way to avoid poking into those internals, but I can do it that way.14:52
jeblairShrews: are you asking about getting that information from within the test?14:53
Shrewsyes14:53
Shrewsi'm going to have to start a builder so that the launch code will work, so maybe i can poke into that object instead14:54
Shrewsi don't think i need to start nodepool14:55
openstackgerritMerged openstack-infra/zuul master: Log a warning when zuul.conf is misconfigured  https://review.openstack.org/25027014:55
jeblairShrews: how about just enhancing the TestNodepol tests (like test_node_assignment)?  they should eventually cover all of this, right?14:56
openstackgerritMerged openstack-infra/zuul master: Tidy up loggers  https://review.openstack.org/22433614:56
jeblairShrews: (so basically, do test this with both a builder and a nodepool)14:56
Shrewsjeblair: yes, the TestNodepool tests will test the overall functionality. But I wanted the test_nodelaunchmanager tests to explicity test the details of the launch manager.14:58
Shrewsi.e, i wanted to make sure ready_nodes and failed_nodes get set correctly in certain situations14:58
jeblairShrews: gotcha.  then, yeah, the plan to borrow the config from a running builder (and/or nodepool) seems sound :)15:00
*** saneax-_-|AFK is now known as saneax15:27
*** abregman is now known as abregman|afk15:29
*** saneax is now known as saneax-_-|AFK16:11
jeblairmordred: just looking at ps7 of 428798 -- do we still need the custom async action plugin?16:20
*** abregman|afk has quit IRC16:20
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: WIP: Implement node launching  https://review.openstack.org/43152316:22
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: WIP: Implement node launching  https://review.openstack.org/43152316:27
*** yolanda_ is now known as yolanda16:41
Shrewsjeblair: I think we should add 'external_id' to your node definition from the spec. Will be needed to delete the instance I believe16:43
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: WIP: Implement node launching  https://review.openstack.org/43152316:51
jeblairShrews: yes, that sounds like an inadvertent omission.16:56
mordredjeblair: yes. we have to use our custom async/normal plugins to inject the log streaming into the test node for shell actions16:57
Shrewspabelanger: were you going to begin on nodepool commands? I'm kind of to the point where I want to at least have 'list' working so I can re-enable the devstack test to see some output17:01
Shrewsi can put that up if you haven't had a chance yet17:02
jeblairmordred: oh, because the 'async' module is the same for both async and not-async?17:02
jeblairmordred: rather, our custom async plugin is run regardless of whether the task is async or not17:03
mordredjeblair: yes. at least for us it is17:03
mordredyup17:03
jeblairmordred: ok.  where's the bit that does the log streaming?17:04
SpamapSjeblair: hm, my changes to land commits in upstream repos may be interacting with other tests. Those repos aren't unique per-test run right?17:04
jeblairSpamapS: upstream repos should be unique per test17:04
SpamapSjeblair: hrm. I have a weird timeout going on now. Only happens when all tests are run.17:05
jeblairSpamapS: before you go too far down a hole -- this might possibly manifest like that: https://review.openstack.org/43045617:05
SpamapSOh that seems highly likely17:06
jeblairSpamapS: (at least, it's probably worth rebasing on that before duing further analysis, because that could potentially cause some nondeterminism)17:06
SpamapSjeblair: it's manifesting in the enablement of test_timer_smtp and it's causing a hard timeout.17:06
SpamapSjeblair: danke, trying exactly that17:06
mordredjeblair: oh - sorry - the command module: zuul/ansible/library/command.py is for logging. zuul/ansible/action/async.py is for timeout17:07
jeblairmordred: okay, that makes more sense!  do we still want that timeout?  at this point it's starting to feel sort of like us just fixing things about ansible... and instead we should maybe just rely on zuul's internal timeout in v3?17:09
jeblair(the 'watchdog timeout' i guess)17:09
mordredyes. I agree - I thnk we shoudl just do the watchdog timeout17:10
jeblaircool, that should simplify some things17:10
mordredyah. thanks for the question - I'd forgotten that's how we broke that out - I'll fix that in just a smidge17:15
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: WIP: Implement node launching  https://review.openstack.org/43152317:18
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: WIP: Implement nodepool 'list' command  https://review.openstack.org/43164717:18
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: DNM: Re-enable devstack test  https://review.openstack.org/43164917:20
Shrews^^^ result of that should be fun17:20
* Shrews goes to get lunch17:20
openstackgerritMonty Taylor proposed openstack-infra/nodepool master: Consume Task and TaskManager from shade  https://review.openstack.org/41475917:22
SpamapSI need a bigger laptop to run zuul tests..17:23
SpamapStop - 09:23:09 up 6 days, 22:45,  2 users,  load average: 8.91, 5.72, 2.9517:23
SpamapSjeblair: so, rebasing on that resulted in a test breaking, and still getting Alarm clock fail.17:24
jeblairSpamapS: is the one you're working on the one that timed out?  does it time out on its own?17:26
*** hashar has quit IRC17:27
SpamapSjeblair: hrm no, I think my rebase went awry somewhere17:28
SpamapSlet me try again17:28
* SpamapS assembles one patch at a time17:28
*** jlk has joined #zuul17:29
SpamapSjeblair: 430456 fails when rebased on feature/zuulv317:30
SpamapShttp://paste.openstack.org/show/598271/17:31
jeblairSpamapS: ah, must have merged an unskip since tests ran.  zuul-connections-multiple-gerrits.conf will need to be updated like the other conf files in 45617:33
SpamapSjeblair: want me to push that up? Changing that moved me forward.17:37
* SpamapS has to detach for a bit to take wife to airport.. bbl17:39
jeblairSpamapS: ++17:39
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Add action plugins to restrict untrusted execution  https://review.openstack.org/42879817:42
mordredjeblair: ^^ that re-cleans up the non-necessary action plugins - still wip though (I should WIP the commit message)17:43
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: WIP Add action plugins to restrict untrusted execution  https://review.openstack.org/42879817:43
jesusaurmordred: thanks for pointing out my comments, i'm slowly starting to get my feet wet in the zuulv3 review pool18:00
jesusaurbut there's a lot to get caught up on18:00
mordred\o/18:01
jeblairmordred: i just realized that at some point in the future (not now, but maybe not too far away) when someone submits a change to a .zuul.yaml file and it has a syntax error, zuul should be able to *leave a line comment on the change pointing out the syntax error in its own configuration*18:08
mordredjeblair: ++18:09
*** jlk has quit IRC18:46
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Implement nodepool 'list' command  https://review.openstack.org/43164718:54
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: DNM: Re-enable devstack test  https://review.openstack.org/43164918:54
Shrewspabelanger: i went ahead and took care of 'nodepool list' command ^^^. You can base any future command enablement off of that18:57
Shrewsjeblair: and if my local enablement of the test_list_nodes unit test can be believed, we might actually be launching nodes now. hoping to see the output from 431649 to verify18:59
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Supply label name to Nodes  https://review.openstack.org/43171919:14
jeblairShrews: i'm getting drunk from toasting all these milestones!19:14
mordredShrews: wait - like, actual nodes?19:17
Shrewsmordred: actual virtual solidly ephemeral nodes19:17
* mordred boggles19:17
Shrewsmaybe. my local laptop doesn't have the resources, so waiting on the gate19:18
* SpamapS back19:23
openstackgerritClint 'SpamapS' Byrum proposed openstack-infra/zuul feature/zuulv3: Split merger and launcher git roots  https://review.openstack.org/43045619:24
SpamapSjeblair: ^ with that one, locally, tests.unit.test_scheduler.TestScheduler.test_dependent_behind_dequeue fails with the hard timeout19:25
pabelangerShrews: ack19:27
pabelangerShrews: I should be able to start later today / tomorrow19:27
SpamapSjeblair: I'm trying it again after a 'git clean -xdf'19:28
SpamapSjust in case19:28
jeblairSpamapS: i think that one is either slow or racy, i'm not quite sure.19:38
SpamapSsame fail on a clean run19:39
jeblairSpamapS: does it fail for you when run on its own?19:39
SpamapSOh that is a big test19:40
SpamapSRan 1 test in 27.684s19:40
SpamapSjeblair: no, works fine on its own19:40
SpamapStestr does have a way to try and see if there are isolation problems19:40
SpamapSjeblair: trying with --analyze-isolation19:43
jeblairSpamapS: it was running close to the timeout before, so i doubled the timeout from 30 to 60s, but it's possible that it's hitting even that when run along with all the other tests due to load.  but unfortunately, i don't know; we don't get logs with hard timeouts (and i checked, we still don't cleanup correctly with soft ones).  so it's also possible there is a race that only shows up under load.19:45
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Set 'cloud' param for integration config file  https://review.openstack.org/43172719:45
SpamapSjeblair: after --analyze-isolation finishes, I'll try with --concurrency=3 which should back the load off a bit19:46
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Supply label name to Nodes  https://review.openstack.org/43171919:46
SpamapSjeblair: with us forking git a lot I wonder if we're just overstepping our CPU resources19:47
SpamapSI do see 74% system CPU load19:47
pabelangerjeblair: do you mind reviewing 430329 and 430339 again, that is for nodepool-launcher19:48
jeblairShrews: btw, i've been thinking: if we're going to keep label around as a concept, we may want to alter the zuul-nodepool protocol to specify 'label' instead of 'type'...19:48
jeblairpabelanger: sure19:49
Shrewsjeblair: maybe. i admit, 'type' had me confused until just recently19:49
Shrewslabel seems much more cohesive19:49
jeblairpabelanger: i'm not sure i follow your comment in 430329... you say you updated system-config to support the new syntax in 430324, but what i'm worried about is 430329 changing what's running on nodepool.openstack.org19:51
jeblairpabelanger: it looks like 430329 would break what is currently running on nodepool.o.o and 430324 doesn't correct that19:52
pabelangerjeblair: Oh, I believe I added install_nodepool_launcher = true, into the wrong node for 43032419:53
pabelangerlet me double check19:54
jeblairpabelanger: oh, no you added it to the right one19:54
jeblairpabelanger: i just didn't realize that snaked through to do the same things that are being removed in 43032919:55
jeblairpabelanger: i'm re-evaluating my comment :)19:55
pabelangerYa all the layers we have in puppet are starting to get a little confusing :)19:55
pabelangerI went cross eyed yesterday with zuul19:55
jeblairpabelanger: partly this is my fault because of the emergency launcher split.  but not entirely.  ;)19:55
pabelangerI do agree, there is a chance for breakage. so extra reviews are most welcome19:56
*** Cibo_ has quit IRC19:57
jeblairweird, why do i still have a -1 on 430329?  that was 4 patch sets ago.19:57
jeblair+2 now19:57
jeblairpabelanger: re 430324 was there not already a nodepool-launcher log config file?19:58
Shrewsdang. either the node didn't launch, or the 'list' command isn't working20:00
pabelangerjeblair: I think that is crud, confirming20:00
jeblairpabelanger: otherwise lgtm20:00
* jeblair lunches20:00
pabelangeryes, crud. Deleted20:01
clarkbpabelanger: why would we want a nodepool launcher on nodepool.o.o at this point?20:04
clarkbisn't that why we have nl01 instead?20:04
clarkband also does it make sense to have people just use openstack_ci::nodepool_launcher rather than adding a new flag to openstack_ci::nodepool?20:05
clarkb(I think thats the more puppety way to do it, though we have been flag happy so this is probably more consistent with how openstackci currently works)20:05
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: DNM: Re-enable devstack test  https://review.openstack.org/43164920:07
pabelangerclarkb: we still need nodepool-launcher on nodepool.o.o, so we don't break production.  Because, we do run nodepool-launcher init.d script20:07
pabelangerwhich just does nodepoold --no-deletes --no-web, etc20:07
pabelangerI was assuming, we'd run nl01 in parallel until we were ready to switch to production20:08
clarkbpabelanger: right isn't that what the split_daemon flag is for?20:08
pabelangerclarkb: it is, but if you look at 430329, you can see how I added the new logic20:09
pabelangerwhich should allow both master and feature/zuulv3 run20:09
pabelangerbut, I'm open to suggestions if there is a better way I am not seeing20:09
pabelangeractually20:10
clarkbright so I guess what I owuld do is not add a new flag20:10
clarkbjust do if split_daemon20:10
clarkband then you are backward compatible20:10
pabelangernow that I am looking at 430329. we need to update our DAEMON args, to use the new patch to nodepool-laundher20:10
jeblairwe should not use 'split_daemon' to mean 'install a v3 launcher'20:10
clarkbthe problem is this isn't compatible for anyone already using split_daemon. Its ok for the new stuff to require new things20:11
clarkbjeblair: I agree20:11
jeblairthat's pretty user-unfriendly20:11
jeblairclarkb: no one but us is using split_daemon20:11
clarkbjeblair: to get a v3 daemon you should just include openstackci::nodepool_launcher which is what nl01 does20:11
*** jlk has joined #zuul20:11
clarkbbasically we have 3 different ways to do 2 things. I am asking that we have 2 ways20:12
clarkbsplit_daemon == pre v3 split daemons. openstackci::nodepool_launcher == v3 launcher20:12
clarkband remove new flag that is confusing20:13
pabelangerI agree, puppet-openstackci is starting to get confusing20:14
jlk"starting"20:17
clarkbpabelanger: my suggestion would be to keep the interface to openstackci::nodepool as is (edit internally as necessary) for pre v3 setup. Then use openstackci::nodepool_launcher for v3 zk speaking nodepool launcher20:19
clarkbpabelanger: but I may be missing soething that complicates doing it that way20:19
pabelangerclarkb: no, I think we could do what you are suggesting, but it means a sight difference on how nodepool-builder and nodepool-launcher could be installed with puppet-openstackci20:23
pabelangerI don't have much preference on which way we go20:23
clarkbpabelanger: because builder already has its own "run a builder" flag?20:24
pabelangerclarkb: ya20:24
clarkbhrm20:24
ShrewsDoes the ubuntu image built by DIB set a password for the ubuntu user?20:34
mordredShrews: I do not believe so20:35
pabelangerwe don't have a ubuntu user do we?20:35
mordredyah - that's an even better point20:35
*** harlowja_ has joined #zuul20:35
mordredShrews: there is a devuser element you can add to the element list which will put your local key information into the image20:36
mordredShrews: for the ones we make for actual nodepool, we have an element that runs puppet and adds the user accounts and keys for all of the infra-root humans20:36
*** harlowja has quit IRC20:37
pabelangerwe did something recently for tripleo too, to allow root user SSH key or password20:37
pabelangertrying to find the commit20:37
clarkbpabelanger: glean already does it, just had to allow ssh to root iirc20:38
clarkbpabelanger: so if you config drive + glean + nodepool dib image you cna ssh as root20:38
Shrewsi'm just trying to figure out how to setup my nodepool.yaml to not make nodepoold bork20:38
clarkbwhich makes the hardest part of that figuring out config drive20:38
pabelangerya, maybe this was for console password20:38
Shrewsbut, i don't think i can actually do this locally20:38
clarkbShrews: you mean the ssh into node test?20:39
Shrewsclarkb: yeah20:39
clarkbShrews: you just have to make your dib build create a user and inject a key, the devstack plugin does this20:39
clarkbI think using devuser?20:39
pabelangerya, we use that20:39
Shrewsah, i see it now. thx20:41
clarkbpabelanger: back to puppeting things. Can we make it so that split_daemons is the thing for launcher pre v3 and have a flag for proper launcher post v3? I think most of my confusion is in how those are getting smushed together20:43
clarkbpabelanger: but that way we are consistent as far as if you want new thing flip flag, if using old thing you are fine as is20:43
pabelangerclarkb: sure, if we are okay with the duplicate code for now20:47
*** jlk has quit IRC20:50
clarkbpabelanger: what parts are duplicated (maybe this is actually what I am confused on)? The old launcher is run nodepoold with flags, new launcher is its own separate daemon without selective bits disabled right? The overlap is that they both need init scripts?20:51
*** jlk has joined #zuul20:51
pabelangerclarkb: so, I was thinking we'd create openstackci::nodepool_launcher class, by moving the current code from openstackci::nodepool into it20:53
pabelangeraside from the new DAEMON syntax, we could reuse everything from today20:53
clarkbgotcha20:53
pabelangerif I am understanding you right, you want to keep openstackci::nodepool un touched20:54
pabelangerbut still okay with openstackci::nodepool_launcher20:54
clarkbpabelanger: no I am ok with adding the nodepool_launcher to nodepool (wasn't originally but you pointed out we do that for the builder)20:54
clarkbbut make it v3 specific, right now I think its straddling both v2 and v3?20:54
pabelangerright20:54
clarkbeg if you don't have it set then your old split daemon setup will stop working too20:54
pabelangerya, so I tried to do that, but it actually meant a lot more puppet code, because of duplicate Class[nodepool_launcher] things20:55
pabelangerso20:55
pabelangerif we don't update openstackci::nodepool, keep the original code, then add nodepool_launcher.pp, I think we'll be okay20:56
pabelangerthen, after v3 lands, we can go back and dedupe20:56
SpamapSjeblair: weirdly enough, setting concurrency to 2 made things _much_ worse.21:02
clarkbpabelanger: ok. I think the biggest thing to avoid would be not taking the opportunity to make the interface to using v3 better as we roll it out. even if maybe that means a little duplication in places for a while21:02
clarkbpabelanger: and I am pretty sure puppet is trying to push towards more composable bits rather than single thing alreayd composed iwth all the flags21:02
SpamapSjeblair: I'd have expected it to take twice as long, but it's at 15 minutes and lots of fail spewed21:03
SpamapSjeblair: aha!21:16
SpamapSit failed soft21:16
SpamapShttp://paste.openstack.org/show/59830621:16
SpamapSoh hm.. it cut off21:17
SpamapShttps://gist.github.com/anonymous/e0ffec24a61905b8d67ea3e2d36e2e24 <-- untruncated21:19
SpamapSException: Timeout waiting for Zuul to settle21:19
SpamapS  stderr: 'fatal: repository '/home/clint/tmp/tmpfNCGOh/zuul-test/upstream/common-config' does not exist21:20
SpamapSthat seems like it might be a problem!21:20
SpamapSGitCommandNotFound: Cmd('git') not found due to: OSError('[Errno 2] No such file or directory: '/home/clint/tmp/tmpfNCGOh/zuul-test/tmp3J1ByO/git/org/project3'')21:20
SpamapSguessing there's somewhere else assuming the subdir name21:21
jeblairSpamapS: if that happened after the test shutdown started, that might just be zuul continuing to run during shutdown21:22
jeblairSpamapS: yeah, those errors are all after this:21:26
jeblair2017-02-09 12:45:54,707 zuul.test                        ERROR    Timeout waiting for Zuul to settle21:26
jeblairSpamapS: after that point, all bets are off as tmpdirs may be deleted while things are still running21:26
jeblairSpamapS: looking at that, my current thinking is that maybe we just need to further increase the settle timeout (and maybe we should just do it for that test).  but we should also probably take a close look at what that test is doing, and make sure we haven't broken something in zuul that makes it take much longer than it should.21:30
jeblairSpamapS: (that might best be done with an eye to making sure the INFO log level is useful (because OMG debug) -- cleanup is sorely needed there)21:31
*** Shrews has quit IRC21:35
*** Shrews has joined #zuul21:36
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: WIP: Implement node launching  https://review.openstack.org/43152321:44
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Implement nodepool 'list' command  https://review.openstack.org/43164721:45
Shrewsjeblair: hrm, not quite sure what's going on with node launching. the 'list' command isn't returning any data: http://logs.openstack.org/49/431649/3/check/gate-dsvm-nodepool/6926ac6/console.html#_2017-02-09_20_30_16_09612621:52
Shrewsjeblair: will pick it up again tomorrow21:52
*** harlowja_ has quit IRC21:58
pabelangerShrews: working on nodepool hold command22:02
pabelangerquestions however, we do we default to 0000000000 as the first node id?22:03
pabelangerand not 000000000122:03
pabelangerlike images?22:03
*** harlowja has joined #zuul22:05
pabelangerShrews: also, left a comment on 43164722:07
openstackgerritPaul Belanger proposed openstack-infra/nodepool feature/zuulv3: Update nodepool list to use zookeeper  https://review.openstack.org/43175622:08
openstackgerritPaul Belanger proposed openstack-infra/nodepool feature/zuulv3: Update nodepool hold to use zookeeper  https://review.openstack.org/43175622:09
pabelangerShrews: ^, should I be using a lock?22:09
Shrewspabelanger: it's safer to do so, yes22:17
Shrewsfor the lock question, that is22:17
Shrewspabelanger: as for the node id, i guess just assume the same as images22:18
pabelangerShrews: right, but I don't understand why our images first build is 0000000001 and our first node is 0000000000. Any ideas why that is?  I would have expected both to start at 0122:20
Shrewsjeblair: oh! i just realized why that test isn't working. i have yet to support min-ready, so nothing is being built22:20
Shrewspabelanger: i think we went through that a while back. it has something to do with deep ZK internals22:20
Shrewspabelanger: i thought so far everything was starting on 000022:22
Shrewsbut my memory is likely failing me22:22
pabelangerokay, weird22:22
pabelangerunit tests for images, are 01 right now22:23
openstackgerritPaul Belanger proposed openstack-infra/nodepool feature/zuulv3: Update nodepool hold to use zookeeper  https://review.openstack.org/43175622:23
pabelangernow with locking^22:23
pabelangerI'll move on to unhold, if ^ looks good22:25
Shrewspabelanger: so, waitForNodeRequest returns a new request that should have request.id populated. You can use that instead of the hardcoded 00000000022:26
Shrewsand avoid that whole "guess the number" mess22:26
pabelangerk22:27
Shrewspabelanger: ugh. no22:27
Shrewsit returns the request, not the node. duh. but request.nodes should have the node id22:28
jeblairShrews: aha, so 'list' is successfully failing! :)22:28
* Shrews really should EOD22:28
Shrewsjeblair: yes22:28
Shrewsso i guess that's tomorrow's task22:29
openstackgerritPaul Belanger proposed openstack-infra/nodepool feature/zuulv3: Update nodepool hold to use zookeeper  https://review.openstack.org/43175622:30
Shrewsok. i'm going away 4realz22:32
Shrewsnight22:32
pabelangerlater22:32
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Inherit playbooks and modify job variance  https://review.openstack.org/43048323:27
jeblairmordred: ^ for you to look at tomorrow23:28
jeblairthat should really be two separate changes, but i've been working on it for 2 days, so really just wanted to push something up.  if folks need me to split it, i can.23:29
jeblairit makes major changes to the Job class, but i think they're worth it.  it clarifies a lot of gray areas, and i'm pretty sure i can actually explain how job inheritance and variance work now.23:31
mordredjeblair: ++23:43
mordredjeblair: I think the most important outcome is a clear and succinct description of job inheritance and variance23:43
mordredrbergeron: ^^ btw - we may be getting close to writing some new-user/end-user related doc type things23:44
rbergeronoh like things i can do? ;)23:46
rbergeroni mean im not on a plane and i love feeling useful23:47
* mordred hands jeblair and robyn some slices of pie he found over yonder23:53
rbergeronpie?23:55
rbergeronmmm pie23:55

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