Tuesday, 2017-02-28

*** patrickeast has quit IRC00:02
*** patrickeast has joined #zuul00:05
*** jamielennox|away is now known as jamielennox00:16
*** saneax is now known as saneax-_-|AFK00:43
jlkjeblair: hi there. I'm looking at v3 history, and the build descriptions stuff went away. That's not back somewhere else right? if there was github stuff to fiddle with this, I can just throw it out?01:14
jlkquick gerrit question, how can I submit a patch (set) that will target the feature/v3 stuff, but uses it's own topic since it'll be it's own set?01:19
mordredjlk: git review -t github01:32
mordredjlk: should work01:32
mordredand put it in the github topic01:32
mordredjlk: the branch has a "defaultbranch" setting in .gitreview01:32
mordredso you don't have to worry too much about the submit-to-feature/v3 part01:32
jlkkk01:32
mordredhowever, fwiw, if you wanted to do that and didn't have the defaultbranch setting in place01:33
mordredgit review -t github feature/v3 would do it01:33
mordred(first unflagged argument is branch to submit to)01:33
* mordred wordvomits on screen01:33
jlkthanks!01:35
jlkoh man, so uh, this refactor of things, well, it's throwing me for a loop in zuul/scheduler.py. It used to iterate over a list of connections and set them up, but now... it doesn't?01:36
jlkI don't know how hte code works to have more than one connection01:36
jlkah, there is a ConnectionRegistry.01:39
dmsimardjeblair: I think I've addressed most of the width-related problems, let me know if that looks better for you ? http://46.231.133.111/reports/index.html (make sure to force-reload/clear cache)02:36
dmsimardjeblair: and pagination can now be deactivated everywhere :)03:57
dmsimardgood night o/03:57
*** saneax-_-|AFK is now known as saneax04:22
*** jasondotstar has quit IRC04:35
*** jasondotstar has joined #zuul04:48
*** abregman has joined #zuul06:10
*** Cibo_ has quit IRC06:16
*** Cibo_ has joined #zuul06:19
*** Cibo_ has quit IRC06:37
*** saneax is now known as saneax-_-|AFK06:53
*** saneax-_-|AFK is now known as saneax06:56
*** isaacb has joined #zuul07:43
*** bhavik1 has joined #zuul07:59
*** bhavik1 has quit IRC08:26
*** hashar has joined #zuul08:30
*** bhavik1 has joined #zuul08:50
*** gk-1wm-su has joined #zuul09:55
*** Cibo_ has joined #zuul10:04
*** isaacb has quit IRC10:06
*** gk-1wm-su has quit IRC10:09
jktuh-oh, it seems that projects which are not anonymously readable over https such as this one, https://paste.fedoraproject.org/paste/oo6LerfacAbpAjmHJiH1cF5M1UNdIGYhyRLivL9gydE= effectively result in zuul-merger not merging *at all*10:19
*** Cibo_ has quit IRC10:32
*** isaacb has joined #zuul10:33
*** Cibo_ has joined #zuul10:36
*** isaacb has quit IRC11:02
*** hashar is now known as hasharLunch11:45
*** isaacb has joined #zuul11:57
*** Cibo_ has quit IRC12:10
*** fungi has quit IRC12:11
*** fungi has joined #zuul12:18
*** saneax is now known as saneax-_-|AFK12:39
mordredjkt: there is a patch somewhere I saw about using ssh for cloning for all the things ...13:02
mordredjkt: https://review.openstack.org/#/c/200034/ is one13:06
mordredthis does not help your zuul-merger case though13:06
*** hasharLunch is now known as hashar13:22
*** Cibo_ has joined #zuul13:39
*** Cibo_ has quit IRC13:46
jktmordred: hehe, I just spent a few hours reinventing that particular wheel; the end result is quite similar :)13:54
jktbut anyway, the getInfoRefs() doesn't appear to be called from this context at all13:57
jktbut my josb are still being executed against an already-merged tip, see the log at https://paste.fedoraproject.org/paste/s5TThymVIk~FFoD3DNkUol5M1UNdIGYhyRLivL9gydE=13:57
*** openstackgerrit has quit IRC14:03
*** isaacb has quit IRC14:03
* jkt loves the generic name "item"14:03
*** isaacb has joined #zuul14:26
jktright, so this is because new Gerrit sends *two* events instead of just one when a new patchset is updated, the refUpdated comes in a separate event apparently14:30
jktor nope. aargh. coffee.14:34
*** mattclay has quit IRC14:35
*** mattclay has joined #zuul14:35
jeblairjlk: correct, build descriptions are gone (jenkinsism)14:40
*** openstackgerrit has joined #zuul14:46
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Storyboard: Support invalid tasks in update script  https://review.openstack.org/43870414:46
*** mattclay has quit IRC14:49
*** mattclay has joined #zuul14:51
pabelangermorning14:58
*** abregman has quit IRC15:05
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove job trees from pipelines  https://review.openstack.org/43594415:12
*** Cibo_ has joined #zuul15:14
*** Cibo has joined #zuul15:41
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Plumb job variables through to ansible  https://review.openstack.org/43865315:43
*** Cibo_ has quit IRC15:43
jeblairpabelanger, SpamapS: i added testing and fixed a bug it caught ^; i think that's actually ready now :)15:44
*** Cibo_ has joined #zuul15:46
*** Cibo has quit IRC15:48
*** isaacb has quit IRC15:50
*** Cibo_ has quit IRC15:51
*** Cibo_ has joined #zuul15:51
pabelanger+215:57
*** isaacb has joined #zuul16:19
notmorganpabelanger: i was told to ping you this week re pen testing/security/etc for zuul-y-things :)16:27
notmorganpabelanger: figured i'd jump on that now(ish) so we can talk soon(ish) ^_^16:27
pabelangernotmorgan: Yes, it was mentioned.16:28
pabelangernotmorgan: So, we have zuulv3-dev.o.o, which we are running jobs on.  Today, people can propose patches to openstack-infra/zuul project and we'll run those playbooks on zuulv3.16:29
pabelangernotmorgan: For me, we should go though the steps to actually try to get data either onto or off the server some how.16:29
pabelangertoday, we don't have any secrets, aside from a SSH private key16:29
* notmorgan nods.16:29
notmorganpabelanger: i think we can have some fun with that.16:30
pabelangerfor me, we should attempt to pen the server, document them some place, then patch feature/zuulv3 and update unit tests16:30
pabelangerthen, repeat16:31
pabelangerwe have talked about wrapping ansible-playbook into some sort of chroot too, but I still think this step is valid16:31
pabelangerWe also have zuul specific action plugins we also use today, but we just need to test them more and fix them as we go16:32
notmorgani agree across the board16:32
pabelangerSo ya, I've pretty much accepted out ssh private key on zuulv3-dev.o.o is actually public right now16:33
pabelangerso maybe we should work to protect that more first16:34
notmorganyeah. i thnk that is def a good plan16:34
notmorganpabelanger: i think we can agree that exploiting the ssh-key can be excluded from other bits if we're looking at pen, in isolation of chroot-y things.16:37
SpamapSjeblair: hooray for test coverage :)16:38
notmorganpabelanger: so agreeing the key is public is sufficient to say "that is the first item on a (i'm sure) list of concerns"16:38
eggshellSpamapS: o/16:49
*** Cibo_ has quit IRC16:55
openstackgerritJan Kundrát proposed openstack-infra/zuul master: Prepare correct refspec on new Gerrit  https://review.openstack.org/43905716:56
jeblairnotmorgan, pabelanger: that key becoming public is at least annoying enough that i'd rather it not happen, so if we're going to capture the flag, let's use something more harmless.  e.g. /etc/passwd.  :)16:58
notmorganjeblair: exactly16:58
notmorganjeblair: which is why i said we document it as a "known issue" and find something more interesting16:58
jeblaircool17:00
notmorganjeblair: if it's a known flaw(ish), it's uninteresting as long as we track it and address it. once we've addressed it, we can see if we can snag it.17:00
notmorganbut probably in a more isolated environment with a dummy key17:00
SpamapSeggshell: howdy.. so let's talk about test_tags17:00
jeblairnotmorgan: well, the potential flaw would be 'ability to fetch a file outside the job root'.  any file on that system would be sufficient to prove it; the only *interesting* file is the key.  but it's an actual live key, so i'd rather the specific key not be actually exposed.17:01
SpamapSI believe it's time we write a spec about launcher protections.17:02
SpamapSWe need to define the problem really clearly, draw lines, and evaluate what exists.17:02
pabelangerYa, I would say a file, owned by zuul, out side of the jobdir is something we aim for.  /etc/zuul/zuul.conf for example17:02
notmorganpabelanger: ++17:03
pabelangerwe likley don't want to leak that17:03
pabelanger /etc/passwd might be harder, since if we do get that, then isn't that a security issue in the OS?17:03
jeblairpabelanger: nah, /etc/passwd hasn't been a security issue for years17:03
pabelangeroh right, I am thinking of shadow17:04
notmorganjeblair: haha i transposed shadow vs passwd too17:04
notmorganwas in the middle of typing "then we have root escalation issues too"... then re-read the target you set17:04
notmorganpabelanger: ^ ;)17:04
jeblairbut zuul.conf is fine too17:04
pabelangerokay, so before we do some of this, we need to restart nodepool.o.o and setup our nodepool-id logic17:05
eggshellSpamapS: I'm wondering if there's a way to feed a test some extra python in zuulv3 since it seems includes is gone.17:07
notmorganpabelanger: sounds good.17:07
jeblairSpamapS: a spec to describe the container tech would be good.  ultimately both the ansible protections and container tech need to be documented in zuul's docs, so that will go a long way toward that as well.17:07
eggshellSpamapS: gandelman mentioned it might be possible to accomplish something similar in the launcher.17:08
SpamapSjeblair: right, that's a good point. It would be good to describe the problem in general terms, and then describe both solutions, so that we can actually look at where we're intending to overlap, and where both are deficient (or what a user is giving up if they find a need to remove one or the other)17:09
jeblairSpamapS: ++17:09
SpamapSjeblair: and ultimately being able to write those things down for users is adoption Nirvana. :)17:09
SpamapSeggshell: what file are you looking at porting forward?17:10
eggshellSpamapS: tests/fixtures/tags_custom_functions.py17:11
SpamapSeggshell: ah, that's removed in v3 IIRC17:12
SpamapSjeblair: ^^ correct?17:12
SpamapSSeems to me that we should just add the tags to the environment in zuul itself the way we add anything else in.17:13
jeblairSpamapS: yes17:13
jeblairSpamapS, eggshell: http://eavesdrop.openstack.org/irclogs/%23zuul/%23zuul.2017-02-06.log.html#t2017-02-06T20:55:2217:13
SpamapSwow17:13
SpamapSjeblair: your IRC log search fu is... impressive17:13
jeblair(careful, i'm having 2 interleaved conversations there, so follow the adam_g thread)17:13
eggshellawesome, that answers my questions on how v3 is going to handle build tags.17:14
jeblaireggshell: and for context, it's mostly just metadata that we can pass around to analysis tools17:15
jeblairlike "this job is tagged with neutron" so that people can go search for neutron related jobs17:16
eggshellmakes sense.17:16
SpamapSeggshell: so you mostly need to port fixtures/layout-tags.yaml to the newer config format under fixtures/config/single-tenant ...17:18
eggshellSpamapS: that part is (mostly) done.17:18
SpamapSeggshell: sweet17:19
eggshellwhat ends up happening is tags don't get added, so the assertEqual fails since expected results != None17:19
SpamapSeggshell: that's a great place to be failing :)17:23
*** isaacb has quit IRC17:23
SpamapSeggshell: so yeah, now you just need to figure out how to check the ansible variables of a fake build instead of the envvars :)17:23
eggshellah okay, there's the unknown unknown!17:24
SpamapSand then of course, plumb that through17:25
* SpamapS notices we've been using more plumbing analogies lately17:25
notmorganSpamapS: as long as you haven't needed the rotorooter .... :P17:26
eggshellSpamapS: re: check the ansible variables of a fake build    is that something that currently exists in v3 or is a desirable?17:28
SpamapSeggshell: well we definitely add ansible variables to jobs that run. I just don't know if fake build records them in a convenient place like it does environment variables.17:29
SpamapSeggshell: see zuul/launcher/client.py17:30
jeblairSpamapS, eggshell: FakeBuild.parameters['vars'] should have it; might be nice to assign that to FakeBuild.variables or something for convenience17:30
eggshellSpamapS jeblair: thanks for the help!17:33
eggshellshould be able to get going now17:33
*** hashar has quit IRC18:06
openstackgerritPaul Belanger proposed openstack-infra/nodepool master: Fix logic error with nodepool-id  https://review.openstack.org/43909018:15
openstackgerritMerged openstack-infra/nodepool master: Fix logic error with nodepool-id  https://review.openstack.org/43909018:54
*** harlowja has quit IRC20:15
*** harlowja has joined #zuul20:16
dmsimardrbergeron, jeblair: so a question I asked yesterday remained unanswered -- should we draft a spec for Zuulv3 around the needs for a reporting interface ?20:21
dmsimardIt's probably okay if we just end up describing ara if that's what we're looking for but we could end up figuring out what we're missing or how we want to implement it20:22
pabelangerdepends what you are reporting.  Openstack health would be an interface today20:23
rbergerondmsimard: i think the answer was sort of yes, except it's probably more like 3.1, and not in the zuul v3 storyboard, since that's literally "get the thing up for openstack"20:23
rbergeronbut 3.1 -- I don' tthink there's a board yet - but i think something like that, or saying "hey, a whole ecosystem of magical things can hook up to and show zuul stuff" is probably reasonable20:24
rbergeronor i could be crazypants20:24
rbergeronthis happens :)20:24
dmsimardpabelanger: right, so this is a bit what I'm asking20:24
dmsimardthere are opportunities to use ara in an openstack-health/centralized kind of way20:24
dmsimardor in one-off report for single jobs20:24
dmsimardIt could be toggled per job, say, "reporting: yes" as one of the job parameters or something20:25
dmsimardfor example it might not be relevant to have reporting for pep8 things20:25
dmsimarda bit like stackviz vs openstack-health20:26
* rbergeron observes the whole internet freak out over aws-east-1 being down20:26
rbergeronoh, maybe it's s320:28
rbergeronsomething's on fire20:28
clarkbya its s320:28
pabelangerdmsimard: rbergeron: I've had some interest in resultsdb for a while: https://taskotron.fedoraproject.org/resultsdb/results. But haven't done a deep dive yet20:29
clarkbrbergeron: the neat thing is it doesn't affect us so we get to keep working as if nothing was wrong20:29
rbergeronserverless will save them all :)20:29
rbergeronclarkb: exactly. but if you take a break to look at the internet you can see ppl posting many pictures of tire fires and having good giggles20:29
dmsimardpabelanger: unrelated but it's pretty cool to see the actual fedora CI https://openqa.fedoraproject.org/tests/5826220:30
clarkbrbergeron: its good for us because for all of them they can't even use the internet in their spare time20:30
rbergeronclarkb :)20:30
clarkbrbergeron: we don't hav eto worry about boredom20:30
rbergeronclarkb: no kidding. i got asked by one of the weird ... gate transfer things at heathrow - - where i went from BA to American - as part of my "so what do you do, why are you here, where do you live" thing20:31
rbergeron"what do you do in your spare time at home?"20:31
rbergeronand i was like20:31
rbergeron.... i'm sorry, my what? lol funny20:31
clarkbrbergeron: I hear yo uwatch competitive minecraft20:31
clarkbI think that might count20:31
rbergeronclarkb: only when watching my kids do it in person at minecon, otherwise, not so much20:32
*** hashar has joined #zuul20:37
tflinkpabelanger: let us know if you have questions or if we can help with resultsdb20:49
*** adamw has joined #zuul20:49
tflinkdmsimard: acutal fedora CI? that hurts a bit :-P20:50
pabelangerokay, zuul is leaving +1 again. I have restarted nl01.o.o20:50
dmsimardtflink: well, I mean, doing CI on screen captures and stuff -- not in a bad way20:51
tflinkdmsimard: for context, I work on the non-actual CI in fedora20:51
adamwdmsimard: i work on the openQA stuff - it's a fun tool, but just part of our overall testing story, it's not the best tool for every job20:51
adamwdmsimard: also it's written by SUSE, so we don't get any of the credit :P20:52
* tflink was also attempting a joke20:52
tflinkand if you have to explain that it's a joke ... you've failed20:52
dmsimard<3 fedora20:52
clarkbits what tumbleweed uses to do their rolling releases. Seems to work well absed on lack of broken desktop20:52
adamwclarkb: yeah, they're doing neat stuff with it.20:52
adamwfor us it started out as a short-term stopgap for automating release validation tests, it kinda turned out better than we expected, so now we kinda expect it to stick around as one test system among many, for running the kinds of tests it's good at20:53
adamwclarkb: btw, https://www.happyassassin.net/nightlies.html is my 'poor man's tumbleweed' - it's integrated with openQA and autocloud, images that have tests and pass all their tests show up green there.20:54
pabelangerclarkb: got time to review: https://review.openstack.org/#/c/438653/ ? plumbs job variables into ansible20:57
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Configure regional mirrors for our jobs  https://review.openstack.org/43915221:00
*** hashar has quit IRC21:00
rbergeronadamw!! <321:04
rbergeronand tflink too :)21:06
openstackgerritPaul Belanger proposed openstack-infra/zuul feature/zuulv3: Add generic tox job  https://review.openstack.org/43828121:06
jeblairpabelanger: hrm, nl01.o.o is not outputting errors anymore.  i'm afraid we have lost debuggable state by restarting it.  if it happens again, let's not restart it so we can look into it.21:06
adamwrbergeron: ahoy21:06
* adamw is just being openqa batman21:06
pabelangerjeblair: ack21:06
adamw:P21:06
jeblairpabelanger: 2017-02-28 21:09:35,275 DEBUG zuul.AnsibleJob: Ansible output: [ubuntu-xenial] 2017-02-28 21:09:35.141004 | # 127.0.0.1:22 SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.121:09
jeblairpabelanger: that's pretty much continuously being output in the zuul logs21:09
jeblairpabelanger: can you look into that?21:10
pabelangerjeblair: sure21:10
jeblairi HUPd zuul3 to pick up the new config with recheck21:11
jeblair(though, hopefully that wasn't necessary)21:11
mordredjeblair: just the ssh banner line?21:12
jeblairmordred: yep21:12
jeblairassume it's related to keyscan21:12
jeblairor something weird about known_hosts21:12
mordredjeblair: yah21:13
pabelangerhappens after running testr21:14
jeblairpabelanger: yeah, i see that too locally21:14
rbergeronadamw: ossum, im being ansible robyn21:15
rbergeronadamw: but nice to see you and tflink both ;)21:15
adamwhaha21:16
tflinkrbergeron: we're good at lurking :)21:16
* adamw does all the lurks21:16
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove unused mergeChangeQueue method  https://review.openstack.org/43595021:17
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Use hostname in Nodepool requests  https://review.openstack.org/43594921:17
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Clarify Job/Build/BuildSet docstrings  https://review.openstack.org/43594821:17
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add note about pipelines and dynamic layouts  https://review.openstack.org/43594721:17
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove inscrutable TODO  https://review.openstack.org/43594621:17
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Handle merge mode in repeated project configs  https://review.openstack.org/43594521:17
jeblairthat triggered a node_failure on the last change21:18
jeblair2017-02-28 21:18:21,255 DEBUG nodepool.NodeRequestHandler: Declining node request 100-0000000797 because it would exceed quota21:18
jeblairoops, i think we have an edge case in our algo21:18
jeblairer, nope, the algo implementation is wrong21:19
jeblairthat should hit this point:21:19
jeblair# If request < quota and request > available nodes (due to current usage), begin satisfying the request and do not process further requests until satisfied21:19
pabelangercool21:23
pabelangeryay for testing21:23
pabelangerjeblair: have we plumbed the timeout setting off the top of your head21:23
jeblairpabelanger: no21:23
pabelangerk21:23
jeblairpabelanger: i think it's in the job, just not passed to the launcher.  so only work on that needs to happen in launcher client/server21:24
jeblairpabelanger, SpamapS: low-hanging-fruit ^21:24
pabelangersure, I can take a look21:24
jeblairpabelanger: well, i was suggesting that someone else could do it, unless you urgently need it21:25
jeblairShrews: i have filed https://storyboard.openstack.org/#!/story/2000886 and added you as an assignee since i assume you will want to continue work on that when you return from your well-deserved break.  :)21:31
pabelangerjeblair: depends if we want to start testing py27 and coverage jobs, we are right on the edge it looks like21:33
pabelangerjeblair: otherwise, I can make them non-voting for now21:33
pabelangerhttps://review.openstack.org/#/c/438281/ also create our base job, which is working21:33
jeblairpabelanger: there's a 60 minute default timeout currently; i think we can live with that for a bit.21:34
pabelangerjeblair: Hmm, odd. something is aborting the job then21:34
pabelangerlet me figure out why21:34
rbergeronomg21:38
rbergeronjimw came to our ansible meetin :) yay21:38
jeblairmordred: can you review https://review.openstack.org/438653 please?21:40
pabelangerjeblair: oh, hehe. timeout is only 60 (seconds) not 360021:42
jeblairpabelanger: ah, the rest of the time must be in pre/post playbooks which do not yet have timeouts21:43
jeblairpabelanger: sounds like this is going to block you; why don't you go ahead and plumb the timeout through21:44
pabelangerjeblair: sure21:49
mordredjeblair: +A21:54
jheskethMorning21:59
mordredmorning jhesketh !22:00
mordredjhesketh: I feel like you've had a much more tiring time since last I saw you than I have22:00
jheskethHeh, probably. The jet lag was pretty bad coming home. Still not sleeping at right hours22:02
pabelangerHmm22:09
pabelanger.tox/py27/bin/python -m testtools.run tests.unit.test_v3.TestAnsible.test_playbook no longer works for me, I fail to properly find ansible-playbook22:10
pabelangerbut if I source activate, it will work22:10
pabelangerI'll dive into that tomorrow22:10
jeblairpabelanger: that probably never worked.  it needs to be in the path.22:12
jeblairmordred: it would be neat if ttrun could handle that case too.  i have no suggestions as to how.  :|22:12
mordredjeblair: hrm. yeah - I mean, I betcha it could pretty easily add the bin of the venv to the path22:14
jeblairmordred: that'd probably do it22:14
mordredjeblair: how does this look? http://paste.openstack.org/show/600855/22:23
mordredjeblair: maybe I should put ttrun somewhere that I could run tests on it ...22:29
mordredof course, then I'd have to _write_ tests22:30
mordredthat patch happily passes all the tests that exist22:30
rbergeronhappy little passing tests, testing alll the things22:45
* rbergeron isnt sure if she's jack handey, bob ross, or happy fun ball22:46
*** hashar has joined #zuul23:00
openstackgerritMerged openstack-infra/zuul feature/zuulv3: Plumb job variables through to ansible  https://review.openstack.org/43865323:02
*** hashar has quit IRC23:04
SpamapSrbergeron: As long as you're not Eeyore, we'll be fine.23:11
jeblairmordred: that patch looks very plausible!23:16
mordredrbergeron, jeblair, SpamapS: (and anyone else) post live: http://inaugust.com/posts/whats-coming-zuulv3.html email and tweet follow ups coming in just a jiff23:16
mordredjeblair: yay!23:16
mordredjeblair: I _think_ I could just update os.environ and then call subprocess.call and it would work - but explicitly passing it in seemed more explicit23:17
*** saneax-_-|AFK is now known as saneax23:18
mordredhttps://twitter.com/e_monty/status/83671950209208729623:27
mordredrbergeron, SpamapS, pabelanger: ^^ for your retweeting pleasure23:28
pabelanger++23:31
*** adamw has left #zuul23:34
SpamapSmmmmmm bloggy23:44
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Add destructor to SSHClient  https://review.openstack.org/43924323:48
pabelangerboo, there is no way to disable user input for the pause task23:49
mordredpabelanger: I mean - you say that ...23:52
pabelangermordred: Ya, I am basically trying to do sleep 30 in a test for zuul, but fails because of Executing local code is prohibited. Pause will work, but makes our logging all funky, and CTRL commands will get intercepted by ansible23:54
mordredpabelanger: ah - yes. I agree with you23:54
mordredpabelanger: while pause should not _normally_ be a problem for us because there will be no tty23:54
mordredpabelanger: oh - can we remove the tty from our subprocess invocation?23:55
pabelangerya, I'll have to see if we can do that23:55
mordredpabelanger: or maybe even just passing in stdin=None or something23:55

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