Monday, 2019-05-06

openstackgerritTristan Cacqueray proposed zuul/zuul master: web: add OpenAPI documentation  https://review.opendev.org/53554101:05
*** altlogbot_1 has quit IRC02:41
*** altlogbot_2 has joined #zuul02:44
*** altlogbot_2 has quit IRC03:31
*** altlogbot_1 has joined #zuul03:33
*** raukadah has quit IRC04:00
*** chandankumar has joined #zuul04:01
*** badboy has joined #zuul05:22
*** quiquell has joined #zuul06:28
*** abraverm has quit IRC06:53
*** themroc has joined #zuul06:56
ianwI feel like "zuul enqueue-ref --tenant openstack --trigger timer --pipeline periodic --project openstack/example_project --ref refs/heads/master" doesn't work07:04
ianwit requires the --newrev, which i'm not sure if it did before?07:05
*** altlogbot_1 has quit IRC07:13
*** altlogbot_2 has joined #zuul07:19
tobiashianw: as far as I remember it always required newrev, but I didn't use enqueue-ref a lot07:28
*** arxcruz|rover is now known as arxcruz07:37
ianwtobiash: yeah, i'm trying to remember -- the docs say it doesn't07:38
ianwhttps://zuul-ci.org/docs/zuul/admin/client.html#manual-enqueue-examples07:38
tobiashinteresting07:39
*** hashar has joined #zuul07:42
*** abraverm has joined #zuul07:44
*** dmellado has quit IRC07:44
*** dmellado has joined #zuul07:44
*** jpena|off is now known as jpena07:49
*** pcaruana has joined #zuul08:24
*** altlogbot_2 has quit IRC09:11
*** altlogbot_2 has joined #zuul09:17
*** zbr is now known as zbr|rover09:18
quiquellzbr|rover: CI with linter reproducer09:40
quiquellhttp://logs.rdoproject.org/48/20548/22/check/tox-linters/b6ca1c5/job-output.txt.gz09:40
quiquellplease don't add a patch set to the review I am working on it09:40
quiquelljust tell me if you find something09:40
*** themr0c has joined #zuul09:55
*** themroc has quit IRC09:56
*** gtema has joined #zuul10:22
*** gtema has quit IRC10:30
*** themr0c has quit IRC10:34
*** gtema has joined #zuul10:36
*** bhavikdbavishi has joined #zuul10:43
*** gtema has quit IRC11:16
*** gtema has joined #zuul11:17
*** altlogbot_2 has quit IRC11:18
*** altlogbot_1 has joined #zuul11:22
*** jpena is now known as jpena|lunch11:32
*** rfolco|ruck has joined #zuul11:50
*** bhavikdbavishi has quit IRC11:57
*** rlandy has joined #zuul12:11
*** altlogbot_1 has quit IRC12:19
*** themroc has joined #zuul12:20
*** altlogbot_3 has joined #zuul12:21
*** jpena|lunch is now known as jpena12:29
*** pcaruana has quit IRC12:29
*** gtema has quit IRC12:36
*** altlogbot_3 has quit IRC13:15
*** pcaruana has joined #zuul13:16
*** altlogbot_3 has joined #zuul13:17
*** altlogbot_3 has quit IRC13:21
Shrewstobiash: what does it take to enable jemalloc on an ubuntu system?13:23
Shrewsis it enough to just install libjemalloc?13:23
*** altlogbot_1 has joined #zuul13:27
Shrewsmaybe using LD_PRELOAD, I guess13:28
Shrewsah, yep. that's how our zuul executors do it13:29
tobiashyes, installing and ld_preload should do it13:30
*** ianychoi has quit IRC13:48
*** ianychoi has joined #zuul13:52
*** fdegir has joined #zuul13:52
*** ianychoi has quit IRC14:04
arxcruztristanC: around? can we talk tomorrow about the zuul runner? me and rlandy are very interested on it, and we want to test it for tripleo jobs :)14:07
pabelangermorning, if humans are around for reviews this morning. I think we should first land the stack of test improvements at https://review.opendev.org/#/q/status:open+project:zuul/zuul+branch:master+topic:test-improvements14:10
pabelangerthen we should be good to open zuul again to merge new features14:11
rlandyarxcruz: tristanC usually shows up at about 6pm my time. I'll ping him then14:12
*** quiquell is now known as quiquell|off14:15
mordredpabelanger: done14:16
pabelangertyty14:17
mordredpabelanger: thanks for digging in to the flaky tests!14:18
*** ianychoi has joined #zuul14:18
pabelangernp, tobiash was a big help there, I just got the little ones :)14:20
pabelangerbut yah, we should be in much position now14:20
tobiash\o/14:28
ShrewsSo, it feels to me that maybe something external changed in the Nov-Dec timeframe to cause these nodepool issues. A python update or similar... if you look at the builder mem usage graph, we see the same mem usage jump at that point as in the launchers: http://cacti.openstack.org/cacti/graph.php?action=zoom&local_graph_id=63751&rra_id=0&view_type=tree&graph_start=1525617663&graph_end=155715366314:42
ShrewsI don't think there has been any change to the builder code that would cause such a jump14:43
tobiashShrews: did you do the upgrade to bionic at that time?14:44
Shrewstobiash: not sure14:44
Shrewstobiash: no, they are xenial14:45
corvusi'm going to be afk for significant chunks of time this week as i recover from the last 3 weeks and prepare for a presentation coming up soon; i'll try to check in periodically to see if anything is blocked on me, but don't expect a lot out of me this week14:47
openstackgerritMerged zuul/zuul master: Bump tox jobs timeout to 3600  https://review.opendev.org/65677115:20
clarkbcorvus: weshould consider a release with the memory leak fix15:36
corvusclarkb: i can do that now15:36
corvusopendev is running 7e29b8a9106da95f5e654a88def61e43d0138b52 and there is one non-test change past that: "Fix for yappi output"15:38
corvusthat's sort of an advanced-user-only debug tool15:38
corvusshould we just tag 7e29b8a9106da95f5e654a88def61e43d0138b52 or master?15:39
clarkbI'm ok with master if yappi fix is the only non test change15:41
clarkbthose fixes were exercised against nodepool too aiui15:41
*** themroc has quit IRC15:41
*** chandankumar is now known as raukadah15:41
tobiashi'm fine with either15:42
Shrewsi am also fine with a nodepool release (to make pabelanger happy) on commit f58a2a15:44
pabelangeryay15:44
Shrewspabelanger: that does not have your network-per-label change, though15:45
Shrewsb/c that just merged15:45
corvusah cool, i'm glad the logger issue was fixed with an adapter :)15:45
pabelangerShrews: I'm okay with that for now15:46
Shrewsi do hope to restart all nodepool processes today after the jemalloc stuff propogates15:47
corvusfor zuul does this look right?  git tag -s 3.8.1 cff3bc89c90445a055156f91556afa70ab0ebaeb15:47
SpamapShttps://review.opendev.org/587731 <-- hey this looks like an important fix for gear that has been sitting since January.15:48
clarkblgtm15:48
*** abraverm has quit IRC15:49
corvusSpamapS: oh thanks!15:49
SpamapScorvus:np, I only found it because I had to re-do my gertty and scoped down to just zuul+gear ;)15:50
corvuswe will have no release notes for zuul 3.8.1 -- do we want to add a "bug fixes:" note about the memory leak?15:51
corvus(it seems like since that's the main reason for the release, it's probably a worthy enough bug for a note)15:51
SpamapS+115:51
SpamapSas a user I love to see bugfix only releases now and then. ;)15:52
corvusfor nodepool, does this look right?  git tag -s 3.6.0 f58a2a2b68c58f9626170795dba10b75e96cd55115:53
Shrewsyep15:54
openstackgerritJames E. Blair proposed zuul/zuul master: Add release note for memory leak  https://review.opendev.org/65739715:57
corvusclarkb, tobiash, SpamapS: ^15:57
corvusnodepool 3.6.0 pushed15:58
corvus15:58 < openstackgerrit> Merged opendev/gear master: add missing str to bytes conversion for Python3  https://review.opendev.org/58773115:58
corvuslet's merge that release note and tag the result as zuul 3.8.116:00
clarkb+2'd16:01
pabelangerhttp://logs.openstack.org/13/656213/2/check/zuul-tox-remote/12fbed8/testr_results.html.gz16:02
pabelangertest_command has failed a few times now, I think we'll need to dig into why16:03
pabelangerlooks to be related to zuul_stream16:03
pabelangerunfortantely, I don't have much time today (maybe this week) to look into it16:03
openstackgerritMerged zuul/zuul master: Update timeout_handler to check for path first  https://review.opendev.org/65678216:10
Shrewspabelanger: yeah, i've seen that one lately. it confused me16:12
Shrewsi was having issues getting tox remote jobs to run locally before the summit happened16:13
*** mattw4 has joined #zuul16:25
*** hashar has quit IRC17:01
*** jpena is now known as jpena|off17:10
openstackgerritMerged zuul/zuul master: Make test_playbook more robust  https://review.opendev.org/65617717:12
openstackgerritMerged zuul/zuul master: Fix race in test_job_node_failure_resume  https://review.opendev.org/65617817:24
pabelangerzuul-maint: if you could add https://review.opendev.org/655474/ to your review pipeline, that should get us per commit wheels for pypi. A discussion can be found at: http://lists.zuul-ci.org/pipermail/zuul-discuss/2019-April/000892.html17:25
*** jamesmcarthur has joined #zuul17:25
tobiashpabelanger: does this job work with unreleased versions?17:27
pabelangertobiash: yah, it should17:31
pabelangerwhen I looked at build output of our release job, I didn't see anything of concern17:31
pabelangerwe'll propose .dev tarballs, which should be then okay to publish to pypi17:31
tobiashok17:31
*** hashar has joined #zuul17:48
*** jamesmcarthur has quit IRC18:00
openstackgerritMerged zuul/zuul master: Update assertNodepoolState() to retry zk requests  https://review.opendev.org/65621318:15
*** tjgresha_nope has quit IRC18:21
*** tjgresha has joined #zuul18:21
*** tjgresha has quit IRC18:22
openstackgerritTobias Henkel proposed zuul/zuul master: Match tag items against containing branches  https://review.opendev.org/57855718:30
openstackgerritTobias Henkel proposed zuul/zuul master: Use implied branch matcher for implied branches  https://review.opendev.org/64027218:31
pabelangertobiash: do you want to review https://review.opendev.org/655588/18:59
pabelangerhttps://review.opendev.org/655188/ also a fix for github driver if people want to review19:01
*** abraverm has joined #zuul19:14
*** hashar_ has joined #zuul19:32
*** maxamillion_ has joined #zuul19:34
*** quiquell has joined #zuul19:39
*** maxamillion has quit IRC19:39
*** hashar has quit IRC19:39
*** quiquell|off has quit IRC19:39
*** maxamillion_ is now known as maxamillion19:39
*** hashar_ is now known as hashar19:49
pabelangerstarting upgrade to 3.6.0 of nodepool20:04
daniel2So after 3 months of this dang project, my coworker finally wants me to upgrade nodepool to latest and start working with ansible.20:09
daniel2:D20:10
pabelangerdaniel2: nice20:12
openstackgerritMerged zuul/zuul master: Add release note for memory leak  https://review.opendev.org/65739720:15
pabelangerSo, have had a 2nd user not get the depends-on syntax correct for github20:15
pabelangerwhat they end up doing is, copying what they see in github ui20:16
pabelangerso, in this case, by original commit had, depends-on: https://github.com/ansible/awx/pull/379920:16
pabelangerbut github ui renders it as: depends-on: ansible/awx#379920:17
pabelangerso, users then copy that syntax for commit / comment, but zuul doens't work as expected20:17
pabelangertobiash: maybe you have had this issue?^20:17
Shrewspabelanger: oh, b/c the github ui turns that into a clickable link, yeah?20:17
pabelangerShrews: Yah20:18
pabelangergithub magic20:18
pabelangerhttps://github.com/ansible-network/sandbox/pull/3220:18
pabelangerthat is the fqdn for github.com20:18
pabelangerin commit message20:18
pabelangerbut rendered in short form20:18
tobiashYeah, it's bad that github changes this20:20
corvuspabelanger: it may be worth making some documentation you can give to users to highlight that?20:20
tobiashI get frequently  the same question20:20
pabelangercorvus: agree20:20
*** evgenyl has joined #zuul20:30
evgenylHi everyone, is this zuul repo on docker hub an official one? https://hub.docker.com/r/zuul/20:38
evgenylI'm wondering if there are any plans on adding tags for the images and how safe is it to always take the latest?20:45
corvusevgenyl: yes it is!20:47
corvusevgenyl: :latest corresponds to the latest commit.  we generally think that zuul is safe to run continuously deployed; several of us run it that way.20:48
corvusevgenyl: we do plan on tagging releases there as well, but we haven't set that up yet.20:48
*** pcaruana has quit IRC20:51
openstackgerritMerged zuul/zuul master: Make paused status bar blue  https://review.opendev.org/65558820:52
evgenylcorvus: Awesome; do you have any recommendations on zuul installation? I'm thinking about taking the playbooks + docker-compose configs and adjusting them for my needs, or are there some other ready-to-use playbooks available?21:02
*** mattw4 has quit IRC21:05
corvusevgenyl: pabelanger has some playbooks in the "windmill" project, but i don't think they use images (yet?) -- i think they run from pypi releases.  i know some folks are running from images, but i'm not sure if they have published playbooks yet.21:16
corvusevgenyl: i think starting with the docker-compose file is a fine option.21:16
*** Miouge has quit IRC21:16
evgenylcorvus: I see, thank you!21:21
*** mattw4 has joined #zuul21:22
pabelangeryah, I should update testing for docker images again21:24
homeskiI'm setting up the zuul all-in-one server21:41
homeskiI'm see errors in executor.log21:41
homeskiwith permission denied when trying to clone the repos I have set in the tenant config... Yet when I manually try to use the key and ssh command that is failing, it works21:42
homeskiany tips?21:42
*** mattw4 has quit IRC21:43
*** mattw4 has joined #zuul21:44
*** hashar has quit IRC21:45
homeskiactually.. I set executor.private_key_file thinking that is the key being used, but after re-reading docs I believe I'm wrong :)21:50
homeskiI set connection.sshkey for the gerrit driver, but I don't think it's actually being used21:53
*** jamesmcarthur has joined #zuul22:22
homeskifinally got it going... I had git 1.8.x installed.. looks like I needed 2.x22:27
*** jamesmcarthur has quit IRC22:51
SpamapShomeski:that's a good callout.. we may want to list that in the doc22:51
homeskiI'm trying on centos7 .. looks like instead of `sudo yum install -y git` you need `sudo yum install -y git2u-all`22:52
homeskiwhen using the ius repo22:53
clarkbWe run our zuul on xenial which is older git too. I dont think newer git is required22:54
corvuswe have 2.7.4 on our executors22:55
homeskiso all the logs look fine right now .. executor, scheduler, zookeeper, nodepool23:00
clarkbcorvus: huh is that something ubunut keeps up to date maybe?23:01
*** zbr|rover has quit IRC23:01
homeskiwhen I reply 'recheck' on a zuul-job repo, I see scheduler.log spit out "Updating ...'23:01
homeskibut that's it, doesn't seem the node gets launched, or any updates to gerrit by zuul from there23:01
homeskiah nvm, I'm, getting errors when loading zuul-config yaml `extra keys not allowed @ data['failure']['mysql']`23:03
corvushomeski: also in the web interface you should be able to see that error by clicking on the little alarm bell in the top right corner, after navigating to any page for that tenant23:04
corvus(eg, the status page for the tenant)23:05
homeskiok thx, yeah I'm currently mucking around in the terminal23:05
corvusyeah, it's the same info; mostly i wanted to make sure you knew that wasn't the *only* way to see errors like that :)23:06
corvusclarkb: i'll tag the zuul release tomorrow and send out release announcements for both23:07
homeskigot a zuul 'Build succeeded.' comment :)23:12
homeskiin the quickstart guide there are 'code-review, verified, workflow' labels23:13
homeskibut when installing gerrit from scratch, there is only 'code-review'23:13
homeskiis it further setup of gerrit to get those, it23:13
homeskiit's not documented23:14
tristanCrlandy: arxcruz: o/23:17
rlandytristanC: hi23:22
rlandytristanC: we were looking at the zuul runner review again23:23
rlandyweshay: ^^23:23
rlandyas another option to the reproducer the ci team has worked on23:23
rlandytristanC: it looks like there are a still a lot of open questions there23:24
corvushomeski: yes, the zuul-quickstart sets up the Verified label23:25
rlandytristanC: this review ... https://review.opendev.org/#/c/644770/23:25
corvushomeski: https://opendev.org/zuul/zuul/src/branch/master/doc/source/admin/examples/playbooks/setup.yaml#L49-L67  and  https://opendev.org/zuul/zuul/src/branch/master/doc/source/admin/examples/playbooks/project.config#L71-L78  are relevant23:26
homeskithanks!23:27
tristanCrlandy: yes, the final zuul-runner cli isn't fully specified yet23:27
tristanCrlandy: corvus find it too complicated, and I don't know yet how to make it simpler23:29
rlandytristanC: lol - that is exactly the complaint with the reproducer - people find it complicated23:29
rlandythey liked it when we could juts hand them a few playbooks to run23:29
rlandybut we tried that approach and it's not workable23:30
tristanCrlandy: https://review.opendev.org/607082 would give you the list of playbooks to run to reproduce a job23:31
rlandytristanC: ok - I'll leave arxcruz some notes with your answers above. But it looks like we will hot similar problems that we had to solve with the reproducer23:33
tristanCrlandy: i can have a look at the stack again today, and can provide instructions how to set it up with your reproducer env23:33
rlandythanks23:33
weshayrlandy I see.. :)23:36
rlandyweshay: yep - looks like we will hit similar issues23:37
tristanCrlandy: weshay: well, fwiw, the current zuul-runner can reproduce a job with just 2 command (pip install && zuul-runner ...) without needing any services or setup23:39
weshaythat is a bold statement :)23:41
rlandyI guess so could w - run bash script23:42
rlandyit's my understanding that to get the zuul runner to work in all the same situations, the system won;t be any less complicated23:44
weshaytristanC so when we attempt w/ tripleo we can bug you for support?23:48
tristanCweshay: yes sure23:49
weshayk.. we'll poke at it over the next few days23:49
tristanCweshay: i'll update the test-day document with clear instructions23:50
weshaytristanC rock on23:51
*** rlandy has quit IRC23:59

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