Friday, 2017-02-03

jeblairSpamapS: yes, it's all yours as long as you want it.  :)00:00
mordredjeblair: I feel like I should write a script that says "if author == jeblair: +3" ;)00:01
jeblairmordred: hehe -- that would be a bad idea since the *simplest* change i wrote to day has the biggest problem: https://review.openstack.org/42839100:01
jeblairps2 of that caused tests to randomly end up running configuration from other tests00:02
jeblairfun stuff.00:02
jeblairi think ps3 should be safe00:02
mordredjeblair: ok. fine. I'll _read_ them00:06
jeblairthanks, and i'm done touching them for a while :)00:06
mordredsure......00:08
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Make web status text/plain  https://review.openstack.org/42850100:10
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Make web status text/plain  https://review.openstack.org/42850100:11
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Report exceptions in launcher  https://review.openstack.org/42849900:41
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Make web status text/plain  https://review.openstack.org/42850100:58
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add some gearman related debugging  https://review.openstack.org/42853001:20
jeblairthere's still something very strange going on which seems like state leaking between tests :|01:21
jeblair(it's manifesting in the webapp unit tests for some reason that escapes me)01:21
*** anteaya has quit IRC01:57
*** pleia2 has quit IRC01:57
*** pleia2 has joined #zuul01:58
*** anteaya has joined #zuul02:04
*** bhavik1 has joined #zuul05:31
*** bhavik1 has quit IRC05:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 1  https://review.openstack.org/42858205:56
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 2  https://review.openstack.org/42858305:56
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 3  https://review.openstack.org/42858405:56
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 4  https://review.openstack.org/42858505:56
*** saneax-_-|AFK is now known as saneax06:18
*** hashar has joined #zuul09:04
*** Cibo_ has quit IRC10:49
jktnow that cloning/merging is getting moved to the workers in v3, will it work for non-public projects?10:54
jkt(e.g., our company's gerrit requires either SSH or HTTPS-with-auth for git clones; I'm currently "supporting" this by adding the zuul's user to a relevant Gerrit group, and hoping that nobody guesses the merger's git URL in a semi-private v6 network...)10:56
hasharjkt: isn't the merge URL exposed as the ZUUL_URL parameter passed to the job ?10:59
jkthashar: Gerrit ensures that nobody but those who are already autorized have access to the job's log (more or less)11:01
*** yolanda has quit IRC11:08
*** yolanda has joined #zuul11:10
*** hashar is now known as hasharAway11:54
*** hasharAway is now known as hashar12:19
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: WIP: Assign node set to node requests  https://review.openstack.org/42842813:29
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: WIP: Assign node set to node requests  https://review.openstack.org/42842813:41
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Assign node set to node requests  https://review.openstack.org/42842813:50
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Update Node and NodeRequest models  https://review.openstack.org/42873613:50
*** gothicmindfood has quit IRC14:03
*** gothicmindfood has joined #zuul14:03
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Bump post playbook timeout to 30mins  https://review.openstack.org/42874014:03
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Update Node and NodeRequest models  https://review.openstack.org/42873614:04
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: WIP: Assign node set to node requests  https://review.openstack.org/42842814:04
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Fix race in node request state changes  https://review.openstack.org/42874114:04
pabelangerjeblair: mordred: ^ looking for some feedback on a zuulv2.5 issue, our post playbook timeout is hardcoded to 10mins, but kolla needs more time. Are we okay will just bumping the value vs plumbing a properly timeout value config setting?14:05
Shrewsi'm just trying to look as busy as jeblair this morning14:05
Shrewspabelanger: morning!14:05
pabelangerShrews: o/14:05
*** pabelanger has quit IRC14:13
*** pabelanger has joined #zuul14:13
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Assign node set to node requests  https://review.openstack.org/42842814:26
Shrews428428 is about as simple as I can make it, now. refactored most other things out into separate reviews14:28
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool feature/zuulv3: Assign node set to node requests  https://review.openstack.org/42842814:31
Shrewsand finally un-WIP'd14:31
pabelangeryay14:34
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: [WIP] Add reporter for Federated Message Bus (fedmsg)  https://review.openstack.org/42686114:58
jeblairjkt: yes, in fact, that's one of the main reasons we're doing it -- but the merging isn't moving to the workers it's moving to the zuul-launcher, a long-running daemon on a controlled and protected server.  the zuul-launcher will then push the repos onto the test node (ie, worker).  so only the server running zuul-launcher needs the gerrit creds.15:18
jeblairpabelanger: yeah, i think hardcoding is fine.15:19
*** saneax is now known as saneax-_-|AFK15:19
pabelangerjeblair: great15:20
*** Cibo_ has joined #zuul15:23
jktjeblair: sweet, thanks (and now I know what you meant by the multi-tenancy in some slides)15:24
jeblairjkt: yeah, doing it this way makes multi-tenancy much more feasible too15:25
*** Cibo_ has quit IRC15:30
*** Cibo_ has joined #zuul15:31
*** bhavik1 has joined #zuul15:32
*** bhavik1 has quit IRC15:40
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: [WIP] Add reporter for Federated Message Bus (fedmsg)  https://review.openstack.org/42686116:17
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Add action plugins to restrict untrusted execution  https://review.openstack.org/42879816:19
mordredjeblair: there is first (almost certainly non-working) pass16:19
*** Cibo_ has quit IRC16:20
*** hashar has quit IRC16:22
*** hashar has joined #zuul16:25
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: [WIP] Add reporter for Federated Message Bus (fedmsg)  https://review.openstack.org/42686116:48
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Add action plugins to restrict untrusted execution  https://review.openstack.org/42879816:51
mordredjeblair: ok. amazingly enough that actually passes its test locally :)16:51
jeblairmordred: \o/16:52
*** yolanda has quit IRC17:03
*** yolanda has joined #zuul17:06
openstackgerritMonty Taylor proposed openstack-infra/zuul feature/zuulv3: Add action plugins to restrict untrusted execution  https://review.openstack.org/42879817:07
mordredjeblair: ^^ updated tests to test both positive and negative (copy works when it should and doesn't when it shouldn't)17:07
jeblairsweet :)17:08
mordredjeblair: structually speaking, that's pretty much all of the pieces for blocking execution via action plugins - only thing left there is to finishing putting in blocking action plugins for all of the things that do local action17:08
mordredjeblair: and then we need to block local_action/connection=local/host: localhost - which will be different and I need to noodle on17:09
mordredjeblair: I _think_ a broken connection plugin that overrides the normal local connection plugin is likely the most resilient - but I need to play17:10
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: [WIP] Add reporter for Federated Message Bus (fedmsg)  https://review.openstack.org/42686117:11
*** hashar has quit IRC17:17
*** EmilienM has quit IRC17:56
*** clarkb has quit IRC17:56
*** gundalow has quit IRC17:56
*** tristanC has quit IRC17:56
*** gundalow has joined #zuul17:56
*** tristanC has joined #zuul17:56
*** clarkb has joined #zuul17:56
*** cinerama has quit IRC17:56
*** dmsimard has quit IRC17:56
*** cinerama has joined #zuul17:56
*** dmsimard has joined #zuul17:57
*** EmilienM has joined #zuul17:57
jeblairi apologize for all the times i'm going to push up a bunch of DNM patches today.  i'm chasing down a very elusive test bug.18:00
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 3  https://review.openstack.org/42858418:00
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 4  https://review.openstack.org/42858518:00
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 1  https://review.openstack.org/42858218:00
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 2  https://review.openstack.org/42858318:00
*** Cibo_ has joined #zuul18:14
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 3  https://review.openstack.org/42858418:22
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 4  https://review.openstack.org/42858518:22
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 1  https://review.openstack.org/42858218:22
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 2  https://review.openstack.org/42858318:22
*** Cibo_ has quit IRC18:29
*** Cibo_ has joined #zuul18:33
Shrewsjeblair: in the integration test, i *think* we might need to put zuul and np on the same page as far as images/providers. I see in the builder logs images being created with names different from what zuul is sending.18:40
Shrewsb/c i sort of half-expected (hoped?) that test_node_request would have worked with https://review.openstack.org/42842818:40
jeblairShrews: yeah, we can update the zuul/tests/functional config to use the names nodepool has18:40
Shrewslooks like nodepool only has one (fake-nodepool)18:41
Shrewsi'll see if i can figure out the relationships there18:42
jeblairShrews: or maybe we're dealing with the nodepool label/image split18:42
Shrewsmaybe18:44
jeblairShrews: maybe we should just go with images now (and change the zuul test to match) just to get some basic stuff working, then maybe look into implementing http://lists.openstack.org/pipermail/openstack-infra/2017-January/005018.html before we do the whole label/image mapping thing?18:45
Shrewsyeah18:46
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: DNM: Test coalescing zuul and nodepool images  https://review.openstack.org/42885818:48
Shrewslet's see what that does18:48
Shrewswell, it still won't pass b/c my change hasn't merged. jeblair: would a Depends-On work in this case? making 428428 depend on 428858?18:49
Shrewsfor the experimental test, that is18:49
jeblairShrews: yep18:49
Shrewscool18:50
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: DNM: Test coalescing zuul and nodepool images  https://review.openstack.org/42885818:51
*** Cibo_ has quit IRC18:54
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 3  https://review.openstack.org/42858418:56
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 4  https://review.openstack.org/42858518:56
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 1  https://review.openstack.org/42858218:56
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: DNM test 2  https://review.openstack.org/42858318:56
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Fix Job class variable modification  https://review.openstack.org/42885918:56
Shrewsjeblair: OMG   http://logs.openstack.org/58/428858/2/experimental/gate-zuul-nodepool/afa0e31/testr_results.html.gz18:56
jeblairi think i might have found the tricky bug ^ (428859)18:56
pabelangerShrews: w00t18:57
jeblairShrews: dude.18:57
jeblairShrews: were on the cusp of being able to run actual code on actual nodes.  :)  we're going to have fun at the ptg!18:57
ShrewsRIGHT?!!!  last piece left is actually launching nodes and some sort of cleanup thread18:58
Shrewsi'm sure that sounds simpler than it will actually end up being18:58
jeblairShrews: *hopefully* after 6 years we have some working code to launch nodes :)18:59
jeblair(mostly working)18:59
Shrewsjeblair: yeah, though there is a lot of cruft around the actual launch i need to disect18:59
mordredjeblair: ah! nice19:00
Shrewsplus, i'd like to try and support terminating launches, if possible19:00
Shrewsduring shutdown19:00
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Coalesce zuul and nodepool images in integration  https://review.openstack.org/42885819:01
jeblairShrews: we may value quick shutdown (with later cleanup) more than clean shutdown.... when we restart nodepool, we usually want it to be fast.19:02
Shrewsjeblair: *nod* I haven't looked to see what it does currently.19:03
jeblairShrews: it might be nice to have an option for a clean shutdown, but we need to handle the leak case anyway, and i'd say most of the time we (openstack) would probably choose to use the unclean shutdown.19:03
jeblairShrews: the short version of the current thing is that it exits quickly with no preparation.  then, the next time it starts, it sets all 'building' nodes to 'delete' and lets the cleanup thread deal with it.  i think the new version of that would probably be: a provider's cleanup thread should delete any unlocked node in 'building' state.  so when a provider restarts after an unclean shutdown, the cleanup thread just does that as a matter of course.19:06
Shrewsjeblair: ok19:08
* Shrews celebrates his minor success with a major cup of afternoon coffee & Bailey's19:10
pabelangerexciting!19:12
jeblairneat, my bug fix broke several working tests, so i get to celebrate that with more bugfixes :)19:14
jlkhahah19:15
jeblair(but it *consistently* broke them, so yay!)19:15
mordredjlk: btw - https://review.openstack.org/428798 is part of the "make  it safe to run ansible from the launchers"  work and affects ansible execution. I hear you know something about that ...19:22
* jlk looks19:22
jlkhrm.19:23
jlkso what happens if I want to test my ansible code, which requires use of specific plugins (action or otherwise) ?19:23
jlkDo I set it up so that the test script is ansible that fires off to a node that runs ansible there?19:24
mordredjlk: I think so - I don't think there is any safe way to include those plugins in the zuul context without it becoming a potential attack vector19:25
jlkright.19:25
jlkso this is because zuul is running ansible on the host, not in some VM or containment?19:26
mordredyah - that's right19:26
* jlk ponders throw-away zuul-launcher nodes19:26
jlksingle-use containment19:26
jlkoh but those happen on the merger nodes now, right?19:27
mordredI am as a next step after this going to look at bubblewrap as a way to wrap what's going on here into a container context as well19:27
mordredyah19:27
mordredthat's the thing ... throwaway merger nodes start to get expensive because of all of the git repos19:27
jlkyeah19:27
jlkneed a data volume19:28
jlkbut then you could leave landmines so..19:28
pabelangerif we have external mergers, like today, I think having throw-away zuul launchers would be cool19:28
mordredexactly. containers will help some - but I don't think any of us actually trust them for security containment against directed attacks. I see them as more of a belt/suspenders against accidental oopses (in this case)19:29
mordredthe only use case we've identified so far where it's a problem is the one jlk brought up - and I could imagine providing some glue in the standard lib as a follow up to make ansibling-the-ansible remotely feel non-wonky19:31
mordred(I'm sort of guessing that'll be in the lessons-learned, how do we improve moving forward work19:31
jlkansibling the ansible has been one of my longest wishlist items for Ansible19:31
pabelangerya19:33
jlkmordred: is there any risk of getting callback plugins loaded when zuul is running ansible directly?19:34
pabelangerif a zuul-worker could request a node from nodepool, that could work too19:34
pabelangerrather then, having all nodes online for launcher19:34
pabelangerbut, I can see that getting tricky19:34
mordredjlk: _shouldn't_ be - zuul writes out an ansible.cfg into a temp dir and executes ansible-playbook from that dir19:35
mordredjlk: is there a way to load callback plugins outside of ansible.cfg?19:36
jlkalright. So as long as ansible.cfg can't be modified, or side-loaded, then we should be good, as there is a whitelist of callback plugins to use19:36
mordredlike in a playbook?19:36
mordredyah19:36
jlk"You can activate a custom callback by either dropping it into a callback_plugins directory adjacent to your play or inside a role or by putting it in one of the callback directory sources configured in ansible.cfg."19:37
jlkit's unclear as to if the whitelist will prevent loading random_plugin from a callback_plugins/ directory19:38
mordredyah. callback_plugins in a role directory would be the one we don't have a good way of preventing19:39
jlkthat's a vector to executing user's code directly on a zuul host19:39
pabelangerthat is one of my concerns honestly, the amount of work (effort) that will be needed to protect the zuul-launcher.19:40
pabelangerbut, until we get our first exploit, maybe I am over reacting a little19:41
jlkit's a matter of what user ansible runs as, and what all access that user has. Looks like I can fairly easily cause my own code to be executed via the user running ansible19:45
jeblairpabelanger: i would not say you are overreacting.19:49
jeblairpabelanger, jlk: running arbitrary code on the launcher would almost certainly let you pwn all of zuul or whatever it protects fairly easily.19:49
jlkactually19:50
jlkwhat prevents running a delegate_to: localhost19:50
jlktype task?19:50
jlkthen you could cause any module to execute locally19:50
jeblairjlk: i think mordred had some thoughts on that, including adding a localhost entry to the inventory (but also possibly requiring a custom connection plugin for other ways of saying "run this on localhost")19:51
mordredjlk: yah - the custom connection plugin that overrides the 'local' connection type was one of the things I was considering19:52
mordredjeblair: looks like we may need to inspect roles that we download for execution19:52
jlkhrm19:52
jeblairjlk, mordred: yeah, we can pretty easily check for 'callback_plugins' directories and bomb if that's needed19:53
jlkyeah, because one could also do add_host: whatever, and then delegate_to: whatever19:53
mordredjeblair: if they have a "callback_plugins" dir in them, they can define a callback plugin that will get loaded19:53
mordredjlk: add_host will also be turned off :)19:53
jlkfair enough!19:53
jeblair(this is really good -- we definitely need to make sure all of these are covered.  maybe we should have a pentest event when we think we have them all :)19:54
mordredjeblair: ++19:54
mordredjlk: you can't put action plugins in a role like you can do with callback plugins can you?19:54
jlkLooks like a good list of things to bork on at http://docs.ansible.com/ansible/dev_guide/developing_plugins.html#distributing-plugins19:55
jlkmordred: was just looking that up, and yes you can19:55
jlkthere's a whole list of paths we need to bitch about19:55
mordredyup19:55
mordredexcellent19:55
mordred_definitely_ need to scrub roles for those19:55
jeblairwe have two very flexible systems colliding :)19:55
mordredsquish19:55
jeblairand we should probably start a list of things we need to check on in future ansible releases19:56
jlklike an octopus arm wrestling a squid19:56
jeblair"wrestling"19:56
mordredjeblair: maybe we just search roles for any directory ending in "_plugins"19:56
jeblairmordred: ++19:56
jeblairand yeah, i think the general answer to the question earlier is "if you can't do it on the launcher, then one of the test nodes should be your ansible controller"19:57
jlkhttps://s-media-cache-ak0.pinimg.com/564x/43/fd/3b/43fd3b214c2ae8ab3619e9b0881777de.jpg19:58
mordrednice19:58
jeblaircan we use that in our docs?19:58
mordredjeblair: yah - and a zuul-provided cantrip of some sort to make treating one of the test nodes like your ansible controller19:59
jlkor there's https://thumbs.dreamstime.com/z/squid-attacking-octopus-giant-giant-34655212.jpg19:59
jlkI'm having too much fun with this: http://img08.deviantart.net/c219/i/2015/022/7/f/octopus_vs__squid_by_wolfsrain7249-d8exyit.jpg20:01
jeblairthis is how you perform security analysis on critical infrastructure, right?20:02
jlkevery good vulnerability needs a snazzy logo and name, so yeah20:04
jlkI'm SecEngineering so hard right now20:04
* jeblair lunches20:05
mordredhttps://www.youtube.com/watch?v=x5izINmi5Fg <-- hide and seek with an octopus20:05
*** hashar has joined #zuul21:11
*** hashar has quit IRC22:27
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Put Zuul vars in an ansible vars file  https://review.openstack.org/42436722:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Move job running into own class  https://review.openstack.org/38596422:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add infrastructure for pre/post playbooks  https://review.openstack.org/42598922:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Use ZUUL_TEST_ROOT in launcher  https://review.openstack.org/42839122:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Handle multiple playbook extensions  https://review.openstack.org/42545022:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Fix nodeset return on skipped jobs  https://review.openstack.org/42586522:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add some gearman related debugging  https://review.openstack.org/42853022:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Set job class attributes in __init__  https://review.openstack.org/42885922:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Tests: store debug logs on error  https://review.openstack.org/42794622:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add SourceContext class  https://review.openstack.org/42784622:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Report exceptions in launcher  https://review.openstack.org/42849922:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Use playbooks defined in repos  https://review.openstack.org/42355022:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add playbooks for all test jobs  https://review.openstack.org/42581022:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Implement job aborting  https://review.openstack.org/42630622:34
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Avoid multiple build cancelations  https://review.openstack.org/42847722:35
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Run pre and post playbooks  https://review.openstack.org/42749422:35
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add inheritance debugging  https://review.openstack.org/42906522:35
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add some gearman related debugging  https://review.openstack.org/42853022:50
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Set job class attributes in __init__  https://review.openstack.org/42885922:50
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add SourceContext class  https://review.openstack.org/42784622:50
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Report exceptions in launcher  https://review.openstack.org/42849922:50
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Use ZUUL_TEST_ROOT in launcher  https://review.openstack.org/42839122:50
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Run pre and post playbooks  https://review.openstack.org/42749422:50
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add inheritance debugging  https://review.openstack.org/42906522:50
jeblairthe board is green!23:01
jeblairmordred, pabelanger: ^ those are ready to go in :)23:01
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add action plugins to restrict untrusted execution  https://review.openstack.org/42879823:01
jeblairmordred: ^ rebased on current patchset23:01
jeblairif you need a map, the series starts at 42838923:02
pabelangeryay23:03
pabelangerlooking23:03
*** saneax-_-|AFK is now known as saneax23:35
openstackgerritAdam Gandelman proposed openstack-infra/zuul feature/zuulv3: Re-enable test_file_jobs  https://review.openstack.org/42911523:59

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