Wednesday, 2019-01-09

tristanCcorvus: i haven't, i guess this needs some sort of specs to enable such customization00:03
tristanCcorvus: simplest solution would be a pipeline.resulst_template blob to be formated with builds (list of job name, log url, build url)00:05
tristanCcorvus: or perhaps zuul would provides different template the user can choose from, e.g. results_with_log_urls, or results_with_build_urls00:06
corvustristanC: oh, maybe we should just do it after we require the sql db.  then we're guaranteed it's available.00:11
corvustristanC: i don't think this needs to be customized; i think when the build page is ready (soon), we just make that the result.  users can still set result_url to override it if necessary; but otherwise i don't think having the result link go directly to logs will be desirable.00:12
corvusbut, at the moment, since the sql db is still technically optional, it's tricky.  so maybe we just make the switch after we move to requiring it.00:13
corvus(or, i guess if we're really eager, we could say, if the sql db is present, use the build page url, otherwise use the log url)00:13
corvussorry, earlier i said "result_url"; i meant "success_url"00:13
tristanCcorvus: but that's not backward compatible, users may have automated system to fetch logs url from zuul comment... shouldn't this be a controlled behavior?00:17
corvustristanC: we have an api for automated systems to find logs, that would be a great thing for folks to update to.00:21
corvusand i don't think we've promised indefinite backwards compatability for anything in zuul.00:22
corvusit certainly warrants a release note00:23
clarkbwe can also advertise the zuul submits job method of processing artifacts that openstack uses if people want ideas for alternate implementations00:24
corvusbut in general, our approach in zuul is that you should get the best working system by default; we try to avoid requiring folks opt-in to the good stuff.00:24
corvusclarkb: yeah, that should be fairly robust00:26
corvusif the zuul web app were not entirely client-side js, we could put a <link rel=...> tag in the build page html to point automated systems at the api endpoint for the build; but i'm not sure if we could do that with the hosting structure we have.00:28
tristanCcorvus: it seems like many (if not all) releases introduces subtle changes to user facing functionality... it sounds better to make changes optional in the 3.x branch with a deprecation notice, and wait for a major release to force them by default...00:28
corvusi'm not sure why making changes in releases is bad00:29
tristanCcorvus: iirc, SpamapS is looking forward upgrading zuul without having to change anything else00:29
corvuswhy upgrade if you don't want change?00:30
tristanCcorvus: to get bug fixe?00:30
corvusi'm not sure we can satisfy everyone all the time here00:31
tristanCanyway, forcing the result comment change makes it easier, so i'm fine with it00:31
corvusi think we've been pretty up-front about the idea that zuul is under heavy development and will change rapidly, and is designed to be continuously deployed.  we *do* try to avoid breaking zuul when upgrading, but i don't think we can ever promise not to break external systems that rely on ad-hoc zuul behaviors.00:32
SpamapSI'm not sure what has been ascribed to me?00:32
corvuslike, we're not going to change the zuul job syntax in a backwards incompatible way for fun and without notice.  but i do think we reserve the right to improve the web interface without making a big deal out of it.00:33
tristanCSpamapS: it was about the react interface, you said "< SpamapS> but.. can.. I just change my version pointer.. just once.. and not have to spend 2 hours mopping up? :-P"00:34
SpamapSYes, that was regarding deployment tooling.00:34
corvustristanC: anyway, if you're not in a hurry, i'm sure we can wait until v4, and if you want to put it in v3 with a feature flag, that's fine with me too.  as long as, in the end, we end up with the nice thing as the only and default option.  :)00:34
corvus(but i would totally just +2 a hard switch in v3 as well :)00:35
SpamapSAs in, every time I have upgraded, I've had to move files, deploment rules, etc. etc.00:35
corvusi have to run now00:35
tristanCSpamapS: and if you have a script that scrap zuul comments for logs, then this feature is likely to require some mopping up00:35
SpamapSYeah, I'd be sad if that stopped working suddenly.00:37
SpamapSBut I don't have such a thing currently.00:37
SpamapSSo I personally am OK this time. ;)00:37
SpamapSAnd was just thining I'd like the result url to be somewhere that I can use to find the variables set in the build, so I could use that to set an artifact ID/url/etc to go fetch in a post job later.00:38
SpamapSscraping comments isn't exactly something I'd expect to work perfectly, forever.00:38
clarkbya I think using the api to fetch that data or having jobs trigger followup work as openstack does for log indexing is likely more robust long term00:40
SpamapSYeah I had actually been thinking of doing a PR# based upload to S3 with a json doc for artifacts, but then I saw the build page and that's really what I want.00:47
SpamapStobiash: I'm curious, with your GitHub setup, how do you enforce gating with Zuul? Since it's an app, I can't explicitly restrict branch protections to it, but if I don't let people have write access to the repo, they can't use labels on PR's...01:02
SpamapSKind of feels like we need a way to have Zuul act like a real user so it can have branch protection access, or do something janky like use comment commands to add labels.01:03
*** jesusaur has joined #zuul01:12
tristanCcorvus: forgot to mention, but could we also have a "buildset" endpoint to get all the build associated with an event?01:37
tristanCcorvus: if so, then we may want to have a buildset page and use this is instead of individual build result, then we could have a dashboard similar to travis-ci01:38
tristanCcorvus: it might also be better, as we could display in a single page, the job-output failure of all the jobs01:39
SpamapStristanC: yes please, a buildset endpoint would be fantastic.01:39
SpamapSThat would let us set buildset on the github status.01:39
SpamapS(I'd also like to see if we could get github checks API results in for each build)01:40
tristanCSpamapS: it seems like we should get those individual build result register with the new check api, then we could make the final zuul result comment a single link to the buildset page01:41
SpamapSya that would be cool01:42
*** spsurya has joined #zuul03:46
*** rlandy|rover|bbl is now known as rlandy|rover03:54
*** rlandy|rover has quit IRC04:17
*** bhavikdbavishi has joined #zuul04:22
*** rf0lc0 has joined #zuul04:53
*** jesusaur has quit IRC05:02
*** rfolco has quit IRC05:02
*** sshnaidm has quit IRC05:02
*** rcarrillocruz has quit IRC05:02
*** sshnaidm has joined #zuul05:09
*** rcarrillocruz has joined #zuul05:09
*** jesusaur has joined #zuul05:10
*** jpena|off has quit IRC05:22
*** jpena|off has joined #zuul05:23
*** bhavikdbavishi has quit IRC05:26
*** bhavikdbavishi has joined #zuul05:27
openstackgerritMerged openstack-infra/nodepool master: Add Fedora 29 testing  https://review.openstack.org/61867105:54
*** pcaruana has joined #zuul07:06
*** quiquell|off is now known as quiquelll07:09
*** quiquelll is now known as quiquell07:09
*** hashar has joined #zuul07:41
*** quiquell is now known as quiquell|brb08:00
*** themroc has joined #zuul08:14
*** bhavikdbavishi has quit IRC08:21
*** bhavikdbavishi has joined #zuul08:22
*** hashar has quit IRC08:24
*** quiquell|brb is now known as quiquell08:28
*** gtema has joined #zuul08:40
quiquellGood morning08:41
*** dkehn has quit IRC08:46
*** avass has joined #zuul08:51
*** jpena|off is now known as jpena08:52
*** hashar has joined #zuul08:53
*** quiquell has quit IRC08:53
*** quiquell has joined #zuul08:54
*** quiquell has quit IRC08:54
*** quiquell has joined #zuul08:56
*** rcarrillocruz has quit IRC09:01
*** avass has quit IRC09:18
openstackgerritTobias Henkel proposed openstack-infra/zuul master: WIP: Add spec for scale out scheduler  https://review.openstack.org/62147909:46
*** avass has joined #zuul09:56
avasstobiash: I think you might have made a small mistake with the executor change yesterday.09:57
avassshould have been: for key in (node.get('host_keys') , []): not for key in node.get('host_keys', []): no?09:58
*** bhavikdbavishi has quit IRC10:00
avasstobiash: but that would just be a touple wouldn't it? since I got the update and i still get the same exception. Couldn't find the node class to figure out how it works.10:09
*** panda|off is now known as panda10:18
*** hashar is now known as hasharAway10:46
*** electrofelix has joined #zuul10:58
*** chandankumar is now known as chkumar|out11:39
*** jpena is now known as jpena|lunch12:08
*** AJaeger has quit IRC12:43
*** rf0lc0 is now known as rfolco12:49
*** AJaeger has joined #zuul12:51
tobiashavass: node is a dict so that should be correct12:52
avasstobiash: any chance the problem could be in that I am using static driver?12:53
tobiashah, that's a missing piece of information12:53
tobiashwhat's your nodepool config?12:53
avasswhat do you need?12:54
*** rlandy has joined #zuul12:55
*** rlandy is now known as rlandy|rover12:56
tobiashavass: I think I've found the bug: https://git.zuul-ci.org/cgit/nodepool/tree/nodepool/driver/static/provider.py#n5213:00
tobiashit just returns but is expected to return the list of keys where everywhere else the list of keys explicitly is defaulted to an empty list13:00
*** jpena|lunch is now known as jpena13:04
avassAh, I see13:06
tobiashavass: but could you post your exception in zuul-executor you mentioned earlier?13:10
tobiashI want to understand why my fix from yesterday didn't fix this in zuul13:10
avasshere?13:10
tobiashpaste.openstack.org13:11
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Default host_keys to empty list in static driver  https://review.openstack.org/62947813:11
avasshttp://paste.openstack.org/show/740941/13:11
tobiashin the meantime this should resolve your issue ^13:11
tobiashah now I understand, host_keys is set explicitly to None in nodepool13:13
tobiashand so the default isn't picked13:13
avassah13:13
tobiashso the correct fix is https://review.openstack.org/62947813:14
tobiashShrews: ^13:14
tobiashand this also explains why it works for me because I don't have windows static nodes, only dynamic ones13:15
avassthanks for the help13:21
tobiashno problem13:23
Shrewstobiash: +A'd13:34
tobiash\o/13:34
*** dkehn has joined #zuul13:49
dmsimardthanks for charting the territory for building and publishing draft zuul-web builds during code review14:06
dmsimardmanaged to finally land it for ara as well and it's largely inspired from your work :)14:07
*** hasharAway is now known as hashar14:15
mordreddmsimard: woot!14:19
mordredtristanC: looking at the openapi patch - it occurs to me that it'll be wrong for whitelabeled installs. I don't think we need to block on that necessarily, but it's a thing we should ponder14:31
mordredtristanC: nevermind. you have, in fact, already thought about this :)14:33
openstackgerritMerged openstack-infra/nodepool master: Default host_keys to empty list in static driver  https://review.openstack.org/62947814:34
openstackgerritMerged openstack-infra/zuul master: Clean up command sockets on stop  https://review.openstack.org/62899014:40
mordredShrews: TIL about super() in python3 and am much pleased14:42
openstackgerritMerged openstack-infra/zuul master: Ensure command_socket is last thing to close  https://review.openstack.org/62899514:43
AJaegermordred, pabelanger : on https://review.openstack.org/#/c/511853/ is a -1 by pabelanger from July 2018. pabelanger is that still valid? Could you two discuss the way forward, please?14:54
mordredAJaeger: I believe, based ona  different patch, that we agreed to move forward with the single version for now and come back to refactoring into multiple later15:01
mordredAJaeger: although I'm starting to think that working through the pabelanger rework of the base job into base minimal first might make it easier to test some of the later portions of this stack15:02
*** arxcruz is now known as arxcruz|ruck15:03
*** rlandy|rover is now known as rlandy15:04
Shrewsmordred: is there more context to that statement?15:04
tobiashmordred probably meant that you don't need to write super(Foo, this)15:06
Shrewsi'm going to chalk it up to Random Musing Wednesdays15:06
mordredShrews: I was reading your config refactor patches and yes, as tobiash says, learned that super(Foo, this) isn't needed in python3 any longer15:08
Shrewsah ha15:09
Shrewsi liked my theory better15:09
*** ssbarnea has quit IRC15:10
*** ssbarnea|rover has joined #zuul15:10
*** hashar has quit IRC15:31
openstackgerritMerged openstack-infra/zuul master: Document missing executor stats  https://review.openstack.org/62674915:41
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Enforce max-job-timeout for jobs without configured timeout  https://review.openstack.org/62955215:42
openstackgerritDavid Moreau Simard proposed openstack-infra/zuul-jobs master: Add support for CentOS and RHEL for the install-nodejs role  https://review.openstack.org/62955415:45
*** quiquell is now known as quiquell|off15:45
Shrewsoh that's interesting. i've never seen nodepool never be able to acquire a lock15:47
openstackgerritMerged openstack-infra/zuul master: Fix skipped job counted as failed  https://review.openstack.org/62591015:49
fungiwhere's the source code for the github app? or is that even an actual software thing which would have source code?15:51
*** bhavikdbavishi has joined #zuul15:54
tobiashfungi: in github speech a github app is not necessary a software but more or less a set of settings for webhook urls, auth mechanism15:56
fungitobiash: thanks, i suspected that might be the case as i couldn't find anything which seemed like source code15:56
tobiashyou can define a github app and 'install' it on repos. Installing means that you allow the owner of that github app to access your repo15:57
tobiashthe owner of the github app has a private key that can be used to generate api keys to access these repos15:57
tobiashmost github apps however have some source code15:57
tobiashe.g. zuul itself is the according software part15:58
tobiashthat gets webhooks and can access the api with that private key15:58
*** avass has quit IRC15:58
mordreddmsimard: I think you're going to add a test to that nodejs patch - when you do, maybe also do the include: trick based on os_family like we do other places16:03
*** pcaruana has quit IRC16:03
*** bhavikdbavishi has quit IRC16:04
*** bhavikdbavishi has joined #zuul16:04
*** chkumar|out is now known as chandankumar16:27
fungithanks tobiash!16:33
*** jpena_ has joined #zuul16:36
*** mhu has quit IRC16:38
*** fbo has quit IRC16:39
*** nhicher has quit IRC16:39
openstackgerritPaul Belanger proposed openstack-infra/zuul-jobs master: Add validate-dco-license role  https://review.openstack.org/62956516:39
*** pabelanger has quit IRC16:39
*** jpena has quit IRC16:39
*** pabelanger has joined #zuul16:40
pabelangerfungi: https://review.openstack.org/629565 is a follow up from yesterday dco request16:42
pabelangererr, dco license check request16:42
fungithanks pabelanger!16:42
*** rlandy is now known as rlandy|brb16:46
fungipabelanger: does that need a node, or just checks the commit on the executor?16:47
pabelangerfungi: nope, you can save yourself one from nodepool and just use executor16:52
pabelangerI wonder if we should also add the job into zuul-jobs too16:53
fungiokay, so empty nodeset, got it16:53
pabelangereg: https://github.com/ansible-network/zuul-config/blob/master/zuul.d/jobs.yaml#L7016:53
dmsimardmordred: I started doing the include distro thing16:54
dmsimardBut then realized it's just an additional block16:54
dmsimardI didn't really want to fan out in like 5 different files for adding a new block16:54
*** jkt has joined #zuul16:55
jkthi, I'm trying to deply zuul v3 on centos 7 via ansible. I wonder if someone tested the redhat recipes from ansible-role-zuul?16:55
jktbecause there's apparently no python3-devel on centos+epel, but there's python34-devel etc16:56
pabelangerjkt: no, since centos-7 doesn't have python3 by default. Fedora will work16:56
pabelangerhopefully once centos-8 lands, I'll update the role to suppport it16:56
pabelangersupport*16:56
jktpabelanger: ah, so it's only targetting fedora ATM16:56
jktpabelanger: are you interested in patches which make this work on el7?16:57
jktI used to work in Puppet, and this is my first attempt at ansible to learn some new bits16:57
pabelangerjkt: I'd much rather hold off until centos-816:57
pabelangerthat will be python3 by default16:57
jktpabelanger: but that's like six months in future at least, isn't it16:58
pabelangerjkt: not sure if timeline public TBH. there is RHEL 8 beta, so we could start targeting that16:58
pabelangerjkt: fwiw: fedora works fine, I use it locally for testing16:59
pabelangerand we gate on it16:59
jktpabelanger: don't get me wrong, I would love to get my hands on el8 too, but my existing zuul-v2 + turbo-hipster setup is slowly but steadily going to explode, eventually17:00
jktand waiting for el8 is, well, a nice excuse for me of course, but...17:00
fungiwould the containerized deployments work on centos 7?17:02
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Add role to move docs and artifacts to log root  https://review.openstack.org/62957117:04
mordredcorvus: how's that look? ^^17:04
mordredpabelanger: aren't the software factory folks pulling in a software collection or something for centos support?17:05
clarkbnote zuul needs python 3.5 or greater17:06
clarkbthe type annotation stuff isnt valid in 3.417:06
jktthere's 3.6 in EPEL as well17:07
corvusmordred: lgtm with suggested improvements17:07
*** rlandy|brb is now known as rlandy17:09
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Add role to move docs and artifacts to log root  https://review.openstack.org/62957117:16
mordredcorvus: I have applied your suggested improvements17:16
mordredoh - you know what - one more change17:16
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Add role to move docs and artifacts to log root  https://review.openstack.org/62957117:17
mordredthere. that's simplier17:17
pabelangermordred: yah, software collections. However, I think python gets installed into an odd place /opt maybe?17:18
mordredjkt: 3.6 totally works - I think the majority of deployers are actually running 3.617:19
jlkOff topic, but GitHub has a new hire, VP of Engineering, who's first name is Dana. Her GitHub handle is 'danaiszuul'17:23
dmsimardjkt: for what it's worth, software factory provides packages for zuul on centos 7 but they are built against software collections17:24
pabelangerjlk: nice17:25
*** themroc has quit IRC17:25
SpamapSjlk: April Fools idea: she announces they're replacing all github CI apps with Zuul. "Dana says there is no CI...."17:31
jlklol17:31
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Add role to move docs and artifacts to log root  https://review.openstack.org/62957117:33
mordredSpamapS: ++17:33
pabelangerq: are we on track for a release of zuul / nodepool this week?17:35
clarkbopenstack infra is running fairly up to date versions of zuul and nodepool both17:36
clarkbI haven't noticed any issues with them after corvus fixed the github reconfigure bug and the window scaling node request bug17:37
pabelangercool, I wouldn't mind one to get the new executor zone stuff17:38
mordredtobiash, pabelanger: since you've reviewed the log output stuff before, wanna take a look at 629571? new (simpler) idea is just to have a role that moves things into the logs dir on the executor and not to modify the upload-logs role17:39
mordredthat way the interface is the dirs on the remote node, openstack can apply the new role to upload interim artifacts to logs, but other deployers can choose to deal with interim artifacts in some other way17:40
pabelangermordred: sure, I'll look after I grab some food17:40
mordredpabelanger: sweet - thanks! I think it should make your concern about making upload-logs do to much go away17:41
*** chandankumar is now known as chkumar|out17:42
pabelanger++17:44
tobiashmordred: you're aware that this role will only work within a trusted playbook?17:48
openstackgerritMonty Taylor proposed openstack-infra/zuul-base-jobs master: Add fetch-output to base jobs  https://review.openstack.org/62897517:51
openstackgerritMonty Taylor proposed openstack-infra/zuul-base-jobs master: Ignore errors on ssh key removal  https://review.openstack.org/62897617:51
openstackgerritMonty Taylor proposed openstack-infra/zuul-base-jobs master: Add merge-output-to-logs to base job  https://review.openstack.org/62960417:51
mordredtobiash: yah. it's intended to be used in a base job's post playbook17:51
tobiashmordred: commented17:51
mordredtobiash: ++ will fix17:52
openstackgerritMonty Taylor proposed openstack-infra/zuul-jobs master: Add role to move docs and artifacts to log root  https://review.openstack.org/62957117:52
mordredtobiash: how's that look?17:53
tobiashmordred: lgtm17:53
mordred\o/17:53
*** sshnaidm is now known as sshnaidm|afk18:01
fungipabelanger: when you say the ansible/awx repo is using that dco check job, poking around recently merged pull requests for that repo i'm not seeing that job being run on them18:04
fungifor that matter, it doesn't look like anyone's adding signed-off-by to their commit messages in that repo at all18:06
openstackgerritMonty Taylor proposed openstack-infra/zuul-base-jobs master: Add merge-output-to-logs to base job  https://review.openstack.org/62960418:07
*** gtema has quit IRC18:07
fungior was mordred just saying that ansible/awx is using zuul to gate changes, and you were saying that ansible-network is using that dco check job?18:07
mordredfungi: I think that's maybe what the thing is18:08
fungiyeah, making sense now. sorrt for the confusion!18:09
fungimordred != pabelanger ;)18:09
*** jpena_ is now known as jpena|off18:12
openstackgerritMerged openstack-infra/nodepool master: Extract out common config parsing for ConfigPool  https://review.openstack.org/62164218:14
*** bhavikdbavishi1 has joined #zuul18:15
*** bhavikdbavishi has quit IRC18:16
*** bhavikdbavishi1 is now known as bhavikdbavishi18:16
mordredfungi: wait - really? I kind of thought pabelanger and I were the same person18:16
fungishocking, yes18:17
ssbarnea|roverdoes zuul have a mechanism where it can trigger a job when another one is finishing (and passing some metadata)? like job chaining?18:17
fungiit has job dependencies and the ability to return information ni variables which are supplied in those dependent jobs18:18
fungissbarnea|rover: https://zuul-ci.org/docs/zuul/user/jobs.html#return-values18:19
ssbarnea|roverfungi: any example? i can explain what I want to do and you can tell me if this would be a good/bad idea.18:19
ssbarnea|roveras part of our jobs we produce the reproducer-quickstart.sh script, which is supposed to reproduce the same job execution on a dev machine. This script is currently not tested by CI.18:20
*** bhavikdbavishi has quit IRC18:20
fungii see where you're going with this ;)18:20
mordredyeah - I think that has the potential to be a great idea18:21
ssbarnea|roverI want to start a test-repro job that runs at least one of these, so we would now that the reproducer is ... reproducable :D18:21
fungissbarnea|rover: if the reproducer-quickstart.sh script is archived with the job logs, then you could indeed have a child job which retrieved that from the supplied log url of the parent job and ran it18:21
ssbarnea|roverfungi: this is collected. as long I know the parent job, i should be able to find the file on logs server.  time to make a POC test.18:23
fungissbarnea|rover: yeah, you shouldn't even need to "know" the parent job build, better to just return the log url as part of the zuul_return and then have the child job use the returned url18:24
ssbarnea|roveron the same logic we could delay fat jobs to run after linting is passing in order to lower the load, right?18:24
ssbarnea|roveri clearly need to deploy zuul locally to play with it more18:24
fungissbarnea|rover: yes, also possible, even zuul v2 could do that. we've experimented with it in the past, and some projects do it to a limited degree now, but it's not without its downsides18:24
fungiin particular, 1. the time it takes to return results from the "fatter" jobs is increased by the time to run the "slimmer" ones, 2. it can increase the number of change iterations i the (common) case where you have linting issues but also some deeper functional or integration problem in your patch18:26
fungissbarnea|rover: as for deploying zuul locally, we have container images and a quickstart walkthrough for deploying a fully-integrated zuul+nodepool+gerrit18:27
fungissbarnea|rover: https://zuul-ci.org/start18:29
fungicorvus: did a live demo of that in berlin18:30
pabelangerfungi: ansible-network does, not sure about awx18:30
pabelangerfungi: https://github.com/ansible-network/cloud_vpn/pull/60 for PR for example18:30
fungiyep, figured it out. thanks!18:31
fungithat's actually the precise example pr i passed along ;)18:31
pabelangerha, nice18:31
fungimost recent merged pr for the first pinned repo in your org, so it was an obvious choice18:31
* fungi is nothing if not lazy18:31
jktdmsimard: thanks, but I think I'm OK with installing via pip; I was just wondering if the ansible playbooks are known to work on el7 at all18:33
ssbarnea|roveri found a bug: WARNING: The http_proxy variable is not set. Defaulting to a blank string.18:36
ssbarnea|roverthis was a lie, the http_proxy  variable was defined.18:36
pabelangerjkt: at one time yes, when it was zuul v2.5. But once zuulv3 came along and python3 requirement, testing was removed18:36
ssbarnea|roversomething very weird is happening with gerrit first account creation dialog, probably related to my 1pasword or some other firefox extension: once start typing the Full Name field, the 2nd field (suername) vanishes from the screen! very weird ...18:43
ssbarnea|rovernope, is not browser. i tried with Safari/Firefox/Chrome even in incognito: the username disapears.18:45
fungilooks like it's just referencing whatever the latest gerritcodereview/gerrit image is on dockerhub18:51
fungihttps://hub.docker.com/r/gerritcodereview/gerrit18:51
fungiUpdated 21 days ago18:52
fungiso guessing it's gerrit 2.16.218:52
fungimight be a new gerrit bug you're encountering?18:52
*** electrofelix has quit IRC18:55
ssbarnea|roverfungi: maybe https://youtu.be/1Ni_r7lOLS418:58
fungiwow, yeah that's strange19:00
fungiyou could probably edit the docker compose file to refer to a specific (older) gerrit image and see if it's any better19:00
*** panda has quit IRC19:19
*** panda has joined #zuul19:21
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Enforce max-job-timeout for jobs without configured timeout  https://review.openstack.org/62955219:29
openstackgerritMerged openstack-infra/zuul master: Add cgroup support to ram sensor  https://review.openstack.org/54950619:32
*** hashar has joined #zuul19:43
ssbarnea|roverfungi: interesting discovery, "sudo docker-compose..." did trigger the error about environment variable but if I removed sudo, it worked. this means sudo is hiding it (even you are already root). this means the docs are misleading. We should write "sudo -i docker-compose..." which is ok.19:47
fungiyeah, sudo likely filters out the proxy envvar19:47
fungiyou could configure sudo not to do that, or explicitly copy the value into the sudo environment for that run, or...19:48
fungiby default sudo only carries over a very limited whitelist of envvars from the calling environment19:48
clarkbsudo is used because docker is a privileged process19:49
fungiat least if env_reset is set anyway19:49
clarkbmaybe have a note that sudo will work for many, but if you have special needs (like proxies) then execute it as root or something19:49
fungiaccording to the sudoers(5) manpage, by default the only envvars preserved are TERM, PATH, HOME, MAIL, SHELL, LOGNAME, USER and SUDO_*19:50
openstackgerritSorin Sbarnea proposed openstack-infra/zuul master: docs: Added missing -i on docker-compose up command  https://review.openstack.org/62965219:52
ssbarnea|roveri was tempted to add a Makefile there that so you could easily run it "make run", but i am not sure if people like that.19:53
ssbarnea|roveri was tempted to adopt docker (gerrit) use for git-review testing which now has the vary bad habbit to leave you with a big number of gerrit servers running even after finishing the tests. CPU and memory hog.19:55
ssbarnea|roverclarkb: fungi : i do love the ease of docker testing approach with zuul! thanks.20:04
ssbarnea|roveri found another issue now but I will narrow it down myself, OSError: [Errno 97] Address family not supported by protocol20:05
ssbarnea|roveri probably need to find the right mix of container tags to use, using latest is probably not going to provide a fully working mix.20:06
fungissbarnea|rover: i can't take credit for the docker quickstart. i think it was mostly (or perhaps entirely) corvus who put that together20:08
ssbarnea|roverkudos to all invoved!20:08
ssbarnea|roverthe problem with vanishing username happens even with the 2.14.3 gerrit container20:18
SpamapSNormally you don't need sudo to docker if you are in a group that can access the docker socket20:21
clarkbSpamapS: ya but that isn't recommened aiui as it gives that user fulltime root access ability20:21
clarkb(though not any worse than passwordless sudo)20:22
SpamapSCorrect20:30
ssbarnea|roveri am on mac and docker works very well without sudo, so we could consider removing the sudo from docker-compose command.20:32
ssbarnea|roveri started with gerrit 2.15.7 and the behavior of create account dialog is different now, the username is not disapearing anymore but I am still unable to click save button.20:33
ssbarnea|roverprobably that for testing purposes we should automate the creation of first user account and avoid these bugs.20:34
ssbarnea|rovernot sure if they are bugs in gerrit or only on the way we setup it initially20:34
ssbarnea|rovergood news: switching to old ui allowed me to create the first account20:36
openstackgerritMerged openstack-infra/zuul master: docs: Added missing -i on docker-compose up command  https://review.openstack.org/62965220:43
fungissbarnea|rover: the zuul integration test jobs do automate gerrit admin user account creation i believe20:59
fungilooks like the username is "admin" and the password is "secret"21:08
openstackgerritMerged openstack-infra/nodepool master: Extract common config parsing for ProviderConfig  https://review.openstack.org/62509421:41
*** hashar has quit IRC21:57
*** rlandy has quit IRC23:25
tristanCpabelanger: note that scl are available and provided by CentOS, e.g.: http://mirror.centos.org/centos/7/sclo/x86_64/rh/rh-python36/23:48
tristanCit may not be as easy to use as a system wide python, but python3 is available23:48
openstackgerritJohn Studarus proposed openstack-infra/nodepool master: Work in Progress  https://review.openstack.org/62968823:57

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