Friday, 2019-08-23

*** mattw4 has quit IRC00:19
*** michael-beaver has quit IRC00:35
*** armstrongs has quit IRC01:16
*** mattw4 has joined #zuul01:33
*** bjackman__ has joined #zuul01:37
*** bjackman__ has quit IRC02:17
*** mattw4 has quit IRC02:23
*** noorul has joined #zuul02:35
noorulclarkb: hi02:35
*** noorul has quit IRC02:44
*** noorul has joined #zuul02:45
*** noorul has quit IRC03:04
*** bjackman__ has joined #zuul03:06
*** noorul has joined #zuul03:09
*** bjackman__ has quit IRC03:12
*** noorul has quit IRC03:13
*** bjackman__ has joined #zuul03:56
*** raukadah is now known as chkumar|rover04:04
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Handle sphinx PDF files  https://review.opendev.org/67807704:06
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Handle sphinx PDF files  https://review.opendev.org/67807704:39
openstackgerritFelix Schmidt proposed zuul/zuul master: Improve visualization retry attempts in UI  https://review.opendev.org/67814705:16
*** noorul has joined #zuul05:26
noorulIs there a way to setup zuul so that I can test the changes quickly live?05:27
noorulNow I am using docker-compose. It takes time to build the container.05:28
*** noorul has quit IRC05:36
*** noorul has joined #zuul05:42
*** bjackman__ has quit IRC06:03
*** bjackman has joined #zuul06:04
*** titusjose has joined #zuul06:13
*** saneax has joined #zuul06:18
openstackgerritAndreas Jaeger proposed zuul/zuul-jobs master: Handle sphinx PDF files  https://review.opendev.org/67807706:30
*** jpena|off is now known as jpena06:59
AJaegerzuul-maint, could you review the change above, please? I tested it now and it works...07:09
*** jangutter has quit IRC08:15
*** jangutter has joined #zuul08:33
openstackgerritMonty Taylor proposed zuul/zuul master: Write json log file by seeking and appending  https://review.opendev.org/67671708:41
openstackgerritMerged zuul/zuul-jobs master: Handle sphinx PDF files  https://review.opendev.org/67807708:57
openstackgerritMonty Taylor proposed zuul/zuul master: Write errors from ansible execution into json log  https://review.opendev.org/67672308:59
*** hashar has joined #zuul09:13
mordredclarkb, corvus: I went ahead and updated 676717 to remove the incorrect comment if you feel like re-voting on it09:18
mordredclarkb: and if you coudl review https://review.opendev.org/#/c/676516 - I don't see any reason to not land it and 67671709:19
openstackgerritTobias Henkel proposed zuul/zuul master: Optionally allow zoned executors to process unzoned jobs  https://review.opendev.org/67384010:52
*** rfolco is now known as rfolco|brb11:10
*** rfolco|brb is now known as rfolco11:17
openstackgerritFelix Schmidt proposed zuul/zuul master: Make direct-push configurable on project-level  https://review.opendev.org/67710911:21
openstackgerritFelix Schmidt proposed zuul/zuul master: Implement push job in merger  https://review.opendev.org/67711011:21
openstackgerritFelix Schmidt proposed zuul/zuul master: Push changes in GerritReporter if direct-push is enabled  https://review.opendev.org/67711111:21
*** bjackman has quit IRC11:23
openstackgerritFelix Schmidt proposed zuul/zuul master: Improve visualization retry attempts in UI  https://review.opendev.org/67814711:25
*** jpena is now known as jpena|lunch11:32
*** hashar has quit IRC11:41
*** hashar has joined #zuul12:07
funginoorul: the fastest way to test changes to zuul is to write unit tests which exercise your changes. that has at least a couple of benefits: 1. you don't need to wait for container builds because tox will just reference the files directly from a virtualenv (which also gets cached so it doesn't have to be rebuilt on subsequent tox invocations, and also you can ask it to only run your specific tests so you don't12:14
fungihave to wait for the full battery to complete), and 2. if you push the tests with your changes then you can prevent those features from regressing in the future12:14
funginoorul: another option is to install zuul system-wide and just manually reinstall your updated source (or edit the files directly in /usr/lib/python*), but i expect the same is possible in a container image too12:16
fungibut the unit test approach is nice because you can follow a test-driven development model where you write the test first to describe what behavior you want, and then keep re-testing and fixing your implementation until the test passes12:17
fungiyou can even (ab)use opendev's zuul deployment to this end by commenting out every job except one of the unit test jobs and then tweak the tox configuration to only run your new tests and push up your changes as work in progress and see what the job result ends up being12:19
fungiespecially useful if you're in a situation where you can't easily run the unit tests locally12:19
*** rlandy has joined #zuul12:20
*** rlandy is now known as rlandy|ruck12:20
*** hashar_ has joined #zuul12:23
*** hashar_ has quit IRC12:44
*** hashar has quit IRC12:44
*** jpena|lunch is now known as jpena12:49
*** hashar has joined #zuul13:00
openstackgerritTobias Henkel proposed zuul/zuul master: Annotate QueueItem logger  https://review.opendev.org/67822613:30
noorulfungi: How do I set log level to debug?13:49
funginoorul: https://opendev.org/opendev/puppet-zuul/src/branch/master/files/logging.conf#L1513:50
fungiand make sure there's a corresponding [handler_debug] if you want to redirect it to a different file13:51
fungizuul just uses the python stdlib logging module13:51
fungiso it's a python logging config, not anything zuul-specific13:51
noorulfungi: Where can I set the log_level ?13:57
noorulfungi: Which config file? zuul.conf?13:57
funginoorul: logging.conf13:58
noorulfungi: Is there an example?13:58
fungidid you see the url i posted? that's how we're setting up debug logging in our (opendev) deployment13:58
funginot sure what other sort of example you're expecting13:59
Shrewshttps://zuul-ci.org/docs/zuul/admin/components.html#attr-gearman_server.log_config  may be useful14:00
Shrewserrr, https://zuul-ci.org/docs/zuul/admin/components.html#attr-scheduler.log_config14:00
Shrewsso many configs  :)14:00
* Shrews hopes fungi is bracing for hurricane season14:01
fungiShrews: thanks, i was searching the docs for "logging" and not finding those14:02
fungiand yeah, i need to pull a bunch of plywood out of the shed and get it ready for boarding up windows14:03
fungii just hope i don't end up having to deal with a hurricane when i'm supposed to be at ansiblefest14:03
Shrewsyeah, that would be inconvenient for sure14:04
fungii guess our docs don't actually spell out that zuul uses python logging14:04
funginoorul: https://docs.python.org/3.5/library/logging.config.html is the config specification for those files14:06
fungii'll push up some extra words14:06
Shrewsdon't they? i thought there was something...14:07
Shrewsfungi: ah, yeah, something for nodepool logging (https://zuul-ci.org/docs/nodepool/installation.html#configuration) but not zuul i guess14:08
fungieven better, words i can just copy!14:08
Shrews\o/14:09
fungidoes zuul also support dictconfig format?14:09
Shrewsthat i do not know14:09
fungizuul/ansible/logconfig.py:        logging.config.dictConfig(self._config)14:10
fungigit grep says yes14:10
noorulfungi: I followed the Zuul from scratch guide14:11
noorulfungi: Do I need to start gearman separately14:11
fungizuul from scratch is mostly geared toward the minimum necessary to get zuul running, so is unlikely to incorporate a lot of information on optional configuration14:11
fungigearman should be started automatically in the scheduler container as a child process of the scheduler daemon if you configure zuul to provide a gearman server14:12
noorulfungi: I get the following exception Exception: Cat job <gear.Job 0x7fc7e2669780 handle: b'H:::ffff:127.0.0.1:1' name: merger:cat unique: cb912586b66c4a0eb0444e56bbc7d35e> failed14:13
clarkbmordred: thanks approved the failed/skipped change and +2'd the json editing14:13
clarkbanyone else want to review 676717? I think that may help with memory on executors14:14
funginoorul: i think that means a gearman server is running, but the merger process which attempted to handle that particular concatenation failed. you probably need to look in your merger/executor logs for 0x7fc7e266978014:15
fungithe gearman protocol itself doesn't provide a lot of facilities for communicating detailed failure information, so you have to go hunting for an actual error message at the client end14:16
*** chkumar|rover is now known as raukadah14:24
noorulfungi: executor is not starting14:28
fungithat might be the problem then14:28
openstackgerritJeremy Stanley proposed zuul/zuul master: Document logging configuration schema  https://review.opendev.org/67824314:30
noorulfungi: fixed the executor14:33
noorulfungi: the web is returning 404 when I hit port 900014:33
funginoorul: that's expected, we've had some requests to add an index page to the api but there isn't one yet14:34
fungiactual api calls should not return 404, however14:34
noorulfungi: How do I get to the status page?14:34
openstackgerritMerged zuul/nodepool master: Add a dib-cmd option for diskimages  https://review.opendev.org/67219614:35
fungioh, nevermind, 9000 is not the api socket it's the base zuul-web socket i guess14:35
fungitry /tenants14:36
fungiour deployment redirects from / to /tenants automatically14:36
fungihowever it's all rendered via javascript these days, so you need to make sure that /static/js/ is being served14:37
fungialso /static/css/, probably basically anything in /static14:39
clarkbtristanC: fyi not sure if 672196 affects your non dib building14:39
tristanCclarkb: thanks for the headsup, this will let us specify the custom disk-image-create script explicitely14:42
tobiash\o/ Now I can remove my PATH env var hack :)14:42
funginoorul: on our deployment (opendev) if i fetch http://127.0.0.1:9000/tenants/ from the command-line on the scheduler i see it linking to css and js files which i can also successfully fetch, so that's probably what you want to check14:42
funginoorul: i guess it also does the same without /tenants on ours14:43
tristanCclarkb: tobiash: there is a risk the cli interface change, perhaps we should document and support a stable disk-image-create usage argparse?14:43
tobiashtristanC: that fact is at least documented in that patch14:44
funginoorul: yeah, looks like the redirect from / to /tenants/ must be encoded in the javascript, so checking the base url should work too14:45
tobiashno idea though if it is possible or desired to keep the disk-image-create cli format stable (although I never saw any change that would impact how nodepool calls dib)14:45
clarkbtristanC: you mean parse dibs args in nodepool?14:47
clarkbI dont think we should do that14:48
tristanCclarkb: i mean document how nodepool use the disk-image-create script and add to release note upgrade if that change14:48
tobiashtristanC: If this ever happend we definitely need to add a release note14:50
clarkbon this particular case a test only flag was removed so I think that is fine. Documenting the values present in the string ibterpolation would be good14:50
clarkb(and maybe we can extend it further to make the whole command overrideable)14:51
tobiashright, that seems useful (I did several tries to parse the args correctly on my first wrapper) ;)14:51
tristanCour wrapper is actually just converting the cli arg to ansible vars: https://softwarefactory-project.io/cgit/config/tree/nodepool/elements/virt-customize/disk-image-create14:52
tristanCthus perhaps nodepool could support an ansible playbook to build image, and set the vars directly, e.g.: image_output=/var/... image_formats=['qcow2', ...]14:53
*** mattw4 has joined #zuul14:54
clarkbtristanC: I dont think it should call ansible directly but instead make more than the binary path executable configurable14:54
clarkbthen you can configure ansoble yourself with the correct parameters14:54
tristanCclarkb: that works for me too14:55
clarkband people can use packer or whatever if they want14:55
clarkbas long as the files end up on disk with the correct nameit should work14:55
*** sgw has joined #zuul14:56
noorulfungi: not found15:06
noorulfungi: I think I am missing something15:07
noorulfungi: But I remember following exact steps15:07
funginoorul: i don't know what to suggest off the top of my head, and am waaay behind schedule on things i need to get done today, but hopefully someone else in here has suggestions15:09
noorulIt will be great if someone can help15:09
noorulI followed this https://zuul-ci.org/docs/zuul/admin/zuul-from-scratch.html15:09
clarkbdid you look at zuul-web logs?15:11
noorulclarkb: Yes, http://paste.openstack.org/show/762690/15:12
openstackgerritMerged zuul/zuul master: Set failed, unreachable, skipped statuses in json plugin  https://review.opendev.org/67651615:12
*** hashar has quit IRC15:15
clarkbI'm betting sudo pip3 install . does not build the js ssets15:16
clarkbassuming you ran that command to install zuul15:16
noorulclarkb: Yes, you are right15:17
clarkbhttps://zuul-ci.org/docs/zuul/developer/javascript.html#deploying maybe that helps?15:17
noorulclarkb: but /tenants is also returning 40415:18
clarkbnoorul: yes, those urls serve javascript which render that info in your browser15:21
clarkbthere are separate api urls if you just want the json responses15:21
clarkbtry /api/tenants and /api/info15:22
fungiyeah, i can confirm, `wget -qO- http://127.0.0.1:9000/api/info` works on our scheduler and returns: {"info": {"websocket_url": null, "stats": {"prefix": null, "type": "graphite", "url": null}, "capabilities": {"job_history": false}}}15:23
clarkbour server does have job history, odd that that is false?15:24
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Mark nodes as USED when deleting autohold  https://review.opendev.org/66406015:25
noorulclarkb: That is giving me response15:25
noorulclarkb: So I need to run web on another port15:27
clarkbno15:27
clarkbyou need to build the javascript assets as described at https://zuul-ci.org/docs/zuul/developer/javascript.html#deploying15:28
noorulI think after installing yarn15:29
noorulWe just have to run pip3 install . again15:29
noorulcorrect?15:29
clarkbyou need to run yarn build first15:31
clarkbthen run pip3 install . again15:31
pabelangerif zuul can see yarn, it should buid it15:32
pabelangerlooking at https://opendev.org/zuul/zuul/src/branch/master/zuul/_setup_hook.py15:32
*** jpena is now known as jpena|off15:32
noorulok15:32
pabelangerbuild*15:32
clarkboh cool15:33
clarkbI think we have a few docs updates to make around that in the from scratch and javascript pages then15:33
clarkbfrom scratch should include a install yarn step prior to pip install15:33
clarkband javascript page can mention that if yarn is present it will b called by pip15:33
clarkbnoorul: is that something you might be interested in pushing if your testing confirms that is the fix?15:34
noorulclarkb: Need to get approval from management15:34
noorulclarkb: Right now in the middle of hackathon15:34
noorulclarkb: Trying to make zuul work with stash and demo it15:35
noorulran yarn build and then pip3 install .15:38
noorulrestarted zuul-web15:38
noorulno luck15:38
clarkbdid yarn build succeed?15:38
noorulYes15:39
*** mattw4 has quit IRC15:39
noorulIt says build folder is ready to be deployed15:39
clarkbyou might need to pip install -U . to get pip to "upgrade" it15:39
clarkbit might see that it hasn't changed from its perspective and not update it?15:39
noorulTrying that15:40
noorulSuper15:41
noorulit worked15:41
pabelangeryay15:41
clarkbya so thats a pip thing since the git repo didn't change, the version doesn't change and pip says "I'm done"15:41
*** jamesmcarthur has joined #zuul15:47
noorulShrews: Is there an example /etc/zuul/scheduler-logging.yaml15:57
Shrewsnoorul: i believe fungi gave you a link for an example15:58
noorulThat is .conf15:58
noorulhttps://opendev.org/opendev/puppet-zuul/src/branch/master/files/logging.conf#L1515:58
noorulIn this document https://zuul-ci.org/docs/zuul/admin/components.html#attr-scheduler.log_config15:58
noorulIt mentions yaml15:58
funginoorul: see https://review.opendev.org/67824315:59
fungii pushed that to address our earlier discussion15:59
*** kmalloc is now known as needscoffee16:00
*** needscoffee is now known as needsSoMuchMoreC16:00
Shrewsnoorul: the log_config parameter is contained in the main zuul.yaml file (and can appear in various sections of that file for each service). That parameter should point to the logging .conf file16:00
*** needsSoMuchMoreC is now known as needscoffee16:00
Shrewsi don't know what scheduler-logging.yaml is16:01
Shrewsunless it's the yaml version of the logging configuration16:01
Shrewswe don't use that style afaik16:01
zbrcan someone correct me about: at this moment zuul requires python2 on all nodes, right? Can we make it make it smarter like ansible2.8 where python3 interpreter is also detected and used?16:02
*** jangutter has quit IRC16:03
fungipretty sure even without ansible 2.8 jobs (including the base job) can set the python path16:04
zbrwhat interest me is: to be able to use nodepool images which have only python3 on them, without any "python" or "python2" executable, and be able to use these without having to configure ansible_python_interpreter.16:05
fungiwe do that currently for jobs where we don't want ansible to run python2.716:05
clarkbfungi: I think opendev is still all python216:06
clarkbbut zuul does respect the python version reported by nodepool iirc16:06
fungiwell, if ansible has a feature where it is able to guess what python to use without being told, then that would likely be independent of zuul16:06
zbrfungi: that is exactly what I want: to avoid using py27, in fact I want to remove it from some images we have on rdo.16:06
clarkband jobs may be able to further override from there16:06
zbrfungi: ansible guess very well but only starting with 2.8 :(16:06
zbrthis means that once default is 2.8, the override is no longer needed.16:07
zbrbut there is no other requirement from zuul itself for also having a py27 installed.16:07
zbrthat was my guess too but someone questioned that and needed to double check.16:08
zbrthanks!16:08
clarkbzbr https://zuul-ci.org/docs/nodepool/configuration.html#attr-diskimages.python-path16:11
zbrclarkb: i guess that ideally this should be a list.16:12
clarkbno I think it is to be used to pick a speciric version16:13
clarkbsince you are building the image you know ehat python should be used16:14
zbryep, can be controlled by that no big deal. still that default is quickly becoming outdated.16:15
zbrbut i know that changing a default could alienate people16:15
clarkbwe tried to default to 3 but ansible doesnt reliably work with 3 in all cases16:15
clarkbthe default is largely there to ensure ansible functions aiui then people can opt into 3 when they know ansible will work with it16:16
zbrclarkb: when it was that? or more exactly, which version of ansible. 26-27 work decently well with py3, only bit missing I know about is auto-detection of python3 executable.16:17
clarkbits the roles and libraries aiui not ansible itself16:17
clarkbthough ansible itself had problems in tye past too16:17
zbrbut if some people are using some less-mainstream modules which where not ported... that is another issue.16:17
clarkbansivle core should work now16:17
clarkbits everything else that may not16:18
zbrsure, i guess we can make try to change default in january.16:18
noorulShrews: Maybe doc is out dated16:25
funginoorul: not necessarily outdated, see https://review.opendev.org/678243 which will explain the difference16:30
*** mattw4 has joined #zuul16:31
*** AJaeger_ has joined #zuul16:32
*** AJaeger has quit IRC16:35
*** AJaeger_ is now known as AJaeger16:38
noorulfungi: cool, thanks!16:39
noorulfungi: something new16:40
funginot really new either, merely undocumented16:42
fungiwhich is why i pushed that documentation change16:43
*** saneax has quit IRC16:43
*** saneax has joined #zuul16:45
*** AJaeger_ has joined #zuul16:47
*** AJaeger has quit IRC16:51
*** saneax has quit IRC16:56
openstackgerritRadosÅ‚aw Piliszek proposed zuul/zuul master: Make files matcher match changes with no files  https://review.opendev.org/67827316:59
yoctozeptofungi: ^17:01
*** saneax has joined #zuul17:01
fungineat17:01
yoctozeptoat least it does not suffer from the problems of the predecessor17:01
*** igordc has joined #zuul17:09
*** jamesmcarthur has quit IRC17:11
*** jamesmcarthur has joined #zuul17:11
*** saneax has quit IRC17:13
*** saneax has joined #zuul17:15
*** jamesmcarthur has quit IRC17:22
*** saneax has quit IRC17:31
*** michael-beaver has joined #zuul17:32
pabelangerso, it took a few hours, but we now have a propose-updates job for ansible-network, for helping automate some tasks that require pull requests to be created: https://logs.zuul.ansible.com/ff/ff38d08253a1c797455cb18b599fc5b29c103afd/post/propose-network-content-collector-vyos-vyos/6e5beb9/job-output.html#l606417:38
pabelangernot as nice at gerrit / git-review, but seems to be working17:38
pabelangerwe wrote a collections migration script to move network bits from ansible/ansible into new platform collections17:39
*** dkehn has joined #zuul17:58
*** AJaeger_ is now known as AJaeger18:14
openstackgerritClark Boylan proposed zuul/zuul master: Stop executor if log streamer dies  https://review.opendev.org/67804918:24
clarkbtobiash: ^ is that better?18:24
noorulclarkb: I am getting exception http://paste.openstack.org/show/762695/18:36
noorulI am not sure why it is looking for that file18:38
*** armstrongs has joined #zuul18:39
clarkbnoorul: ssh is how zuul connects to test nodes, it needs an ssh key to do that18:40
titusjoseI am attempting to write a nodepool driver for GCE. Although I was able to follow the existing nodepool driver implementations and figured out that nodepool is using ZK to store the metadata about the resource created on the provider. I am not able to figure out how zuul would be using the metadata(hostname/ip , ssh key etc) about a node with Ansible.18:40
titusjoseCan someone point out on how this plumbing of ansible figuring out the node hostname/ip ssh keys etc for the node returned from nodepool is done?18:41
noorulclarkb: I thought it will be looking at zuul users home folder /var/lib/zuul/.ssh18:41
clarkbtitusjose: zuul submits node requests to nodepool via zookeeper. Nodepool reads those and attempts to fulfill them. If it fulfills them it sends a response to zuul on the node request with those details18:41
titusjoseAnd how does zuul expose those details it got from nodepool in to ansible?18:42
clarkbnoorul: the docker compose stuff uses /var/ssh18:43
clarkbtitusjose: zuul writes an ansible inventory with the information it received from zookeeper from nodepool18:43
clarkbtitusjose: https://opendev.org/zuul/zuul/src/branch/master/zuul/executor/server.py#L654-L686 there18:44
clarkbtitusjose: you shouldn't need to worry about that if the GCE driver in nodepool adheres to the existing interfaces18:44
clarkb(all of that should just work)18:44
noorulclarkb: I am running using the scratch doc18:45
clarkbnoorul: I'm not sure why it chooses that dir but that is the dir it seems to use18:45
clarkbnoorul: what is your configs [executor] private_key_file value set to?18:46
openstackgerritClark Boylan proposed zuul/zuul master: Document js tool installation in scratch doc  https://review.opendev.org/67828618:49
clarkbnoorul: ^ patch to address the problem you ran into earlier18:49
*** armstrongs has quit IRC18:51
openstackgerritClark Boylan proposed zuul/zuul master: Stop executor if log streamer dies  https://review.opendev.org/67804918:53
noorulclarkb: private_key_file=/var/lib/zuul/.ssh/nodepool_rsa18:55
noorulclarkb: The tenant configuration is stored in /etc/zuul/main.yaml18:56
clarkboh sorry this is in the merger process18:56
noorulclarkb: Does that mean, if I have to add a new tenant, I need to restart scheduler?18:57
clarkbno18:57
clarkbthe merger process is going to use the key associated with the gerrit/github/bitbucket connection18:57
clarkbyou need to check the sshkey value of that connection18:57
clarkb(I thought this was the key to ssh to the nodes but it is the key to connect to the git server instead)18:58
clarkbtenant configuration lives in the yaml files which are loaded when triggered to do so18:58
clarkbif you hcange zuul.conf then you hvae to restart18:58
noorulclarkb: https://zuul-ci.org/docs/zuul/admin/zuul-from-scratch.html19:01
noorulclarkb: tenant_config points /etc/zuul/main.yaml19:01
noorulclarkb: I cant see merger section there19:02
clarkbnoorul: in the zuul.conf file19:02
clarkbnoorul: what connections do you have defined in that file?19:03
noorulhttp://paste.openstack.org/show/762848/19:04
clarkbnoorul: it come sfrom line 24 of that file19:04
noorulOh the bitbucket has /var/ssh/zuul reference19:04
noorulclarkb: Regarding tenant config, how can I load it dynamically19:06
fungi`zuul --help` should give you command-line help on the various rpc subcommands. one of them is for reconfiguring19:07
fungihttps://zuul-ci.org/docs/zuul/admin/client.html19:08
clarkbalso sighup against the scheduler works (though the utility command is preferred)19:08
fungier, for some reason i thought there was a reconfig19:08
clarkbfungi: I thought there was too19:08
fungii'm not seeing it in the client doc though19:09
clarkbI think it is zuul-scheduler reconfigure19:09
clarkbnot zuul reconfigure19:09
pabelangerzuul-scheduler full-reconfigure19:09
noorulSo this can be automated using a git repo19:10
clarkbpabelanger: thanks19:10
pabelangerhttps://zuul-ci.org/docs/zuul/admin/components.html#operation19:10
pabelangernoorul: yup, gitops should be fine19:10
fungiaha, i was looking for the wrong cli19:13
*** jamesmcarthur has joined #zuul19:28
SpamapSWith nodepool+aws+cloudimages we tried to bump our min-ready from 0 to 3 and got this19:30
SpamapShttp://paste.openstack.org/show/762851/19:30
SpamapSThis is on 3.8.0, but we saw it on 3.6.something too19:30
SpamapSJust looks like an assumption. AWS has no diskimage ability, thus no attribute.19:31
SpamapSShrews:^ ?19:32
*** jamesmcarthur has quit IRC19:32
*** jamesmcarthur has joined #zuul19:32
clarkbSpamapS: ya it is checking that the image for a label is present. But should only do that check against dib if building images for that label19:33
clarkbthere is a hsort circuit in there though19:34
clarkbSpamapS: https://opendev.org/zuul/nodepool/src/branch/master/nodepool/launcher.py#L1021-L1023 are you missing that config flag?19:34
clarkboh I see I think it is a bug in the aws driver19:35
clarkbSpamapS: https://opendev.org/zuul/nodepool/src/branch/master/nodepool/driver/aws/config.py#L168-L17019:35
clarkbI don't know enough of aws' image management to say if we should always se tthat value to false or not19:37
SpamapSclarkb:well there you go19:37
SpamapSThere's no image mgmt19:37
SpamapSSome day maybe. ;)19:37
SpamapSclarkb:do you want to do the patch? :)19:37
clarkbya one sec19:38
openstackgerritClark Boylan proposed zuul/nodepool master: Set manage_images to false on aws  https://review.opendev.org/67829219:39
SpamapS:-D19:39
fungiwas aws supposed to have image management?19:40
SpamapSI wrote some follow-up code that went nowhere, but it landed originally w/o img mgmt19:40
SpamapSit's possible a git add -p went awry, and then reviewers missed it19:41
*** jamesmcarthur has quit IRC19:43
*** jamesmcarthur has joined #zuul19:45
noorulIs there a documentation for running log server?19:47
clarkbnoorul: the quickstart docs work through it with the docker compose hosted logs server19:49
*** jamesmcarthur has quit IRC19:50
fungizuul itself doesn't provide a log server, but yeah there is an example of one built from conventional parts in the quickstart19:50
fungiyou can also point zuul at a swift object store (or a compatibly-configured ceph deployment apparently)19:50
fungii wouldn't be surprised if someone comes up with other drivers for, e.g., amazon s319:51
noorulclarkb: I am using the scratch doc19:53
noorulclarkb: I am not using docker now19:53
clarkbI know19:53
clarkbI'm saying that that document goes through it, I'm not aware of another document19:53
fungizuul-from-scratch is a walkthrough for setting up zuul, and zuul doesn't itself provide any file server to host logs19:54
noorulfungi: Got it19:54
fungibut it can take advantage of one if you provide it and configure jobs to archive to it19:54
fungizuul-quickstart has a container which provides a log server (with i think sshd and apache?) for the example jobs to archive their build logs on19:55
fungizuul-quickstart also provides a contanier with a gerrit server to be able to trigger events and accept result reporting, but that's technically not a component of zuul either19:56
AJaegerZuul experts, I see on https://review.opendev.org/#/c/678248/ "Unable to freeze job graph: 'NoneType' object has no attribute 'decrypt'" after the change is merged - and the promote job is not run. Any ideas?20:05
clarkbsecrets have the decrypt attribute so that tells me that a secret isn't being set20:06
AJaegerthat would be promote-stx-tox-docs or  promote-stx-api-ref - I'M checking20:07
AJaegerfound it - wrong secret name20:08
*** weshay is now known as weshay_MOD20:10
AJaegerthanks, clarkb for hint20:10
*** jamesmcarthur has joined #zuul20:14
*** jamesmcarthur has quit IRC20:18
*** jamesmcarthur has joined #zuul20:19
*** igordc has quit IRC20:37
titusjoseclarkb: For AWS driver I see providers.[aws].pools.labels.key-name as the keypair that would be used to create an instance. What is the assumption that exists here that Ansible should know to pick up the corresponding private key of the keypair?21:08
clarkbtitusjose: I think it is the other way around. Nodepool is expected to provide the public side of the key that zuul has21:09
*** michael-beaver has quit IRC21:10
clarkbtitusjose: for opendev the way we set it up is to have our image build process bake the public key into authorized_keys for zuul. Then we use the key-name metadata based stuff to add our administrator keys21:10
clarkb(but you could use the more dynamic system to provide keys for the zuul user too)21:10
clarkbpoking at docs that may be something we need to be more explicit about21:14
clarkbI'm not sure where best to expand docs for that https://zuul-ci.org/docs/zuul/admin/components.html#attr-executor.private_key_file seems like the correct reference point but likely to be lost if wanting to know the bigger picture21:19
*** needscoffee is now known as kmalloc21:32
noorulclarkb: I am getting the exception http://paste.openstack.org/show/763007/21:36
noorulclarkb: in executor log21:36
clarkbnoorul: you need to set https://zuul-ci.org/docs/zuul/admin/components.html#attr-merger.git_user_email and https://zuul-ci.org/docs/zuul/admin/components.html#attr-merger.git_user_name in zuul.conf21:38
*** igordc has joined #zuul21:45
*** jamesmcarthur has quit IRC21:46
*** jamesmcarthur has joined #zuul21:48
*** jamesmcarthur has quit IRC21:50
*** jamesmcarthur has joined #zuul21:51
openstackgerritClark Boylan proposed zuul/zuul master: Set git user config in from scratch document  https://review.opendev.org/67831221:54
clarkbnoorul: ^ is a docs update to reflect that21:54
*** jamesmcarthur has quit IRC22:07
*** jamesmcarthur has joined #zuul22:07
*** a5hik has joined #zuul22:12
*** jamesmcarthur has quit IRC22:13
*** rlandy|ruck has quit IRC22:21
*** jamesmcarthur has joined #zuul22:31
*** jamesmcarthur has quit IRC22:37
*** jamesmcarthur has joined #zuul22:39
*** jamesmcarthur has quit IRC22:46
*** jamesmcarthur has joined #zuul22:50
*** igordc has quit IRC23:00
*** jamesmcarthur has quit IRC23:01
*** jamesmcarthur has joined #zuul23:15
*** jamesmcarthur has quit IRC23:17
pabelangerHmm23:19
pabelangeranybody seem this before23:19
*** jamesmcarthur has joined #zuul23:19
pabelangerhttp://paste.openstack.org/show/763008/23:19
pabelanger refs/remotes/origin/HEAD will become dangling!23:19
clarkbpabelanger: I think that means origin deleted what was HEAD?23:20
clarkbdid someone switch from master to devel and delete master?23:20
clarkbsomething like that23:20
clarkbif you delete the repo and force zuul to reclone I would expect that to fix it23:21
pabelangerOh23:21
clarkb(you could also do surgery and update to match the new HEAD23:21
pabelangerI did delete some branches23:21
pabelangerbut not master23:21
clarkbwell whatever head is23:21
clarkb(might not be master)23:21
pabelangerokay, that might be it23:22
pabelangerI deleted a bunch of branches in github23:22
*** jamesmcarthur has quit IRC23:22
pabelangerthat must have messed up mergers23:22
*** jamesmcarthur has joined #zuul23:22
clarkbyou can check what head is by catting it23:25
clarkbthen cross check against your deletions23:25
clarkbbut I think the fix is likely to have zuul reclone23:25
pabelangeryah, I forced zuul to reclone23:26
pabelangershould try and figure out a nicer way to handle that23:27
pabelangerI completely forgot deleting branches affected zuul23:27
clarkbwell I think it is only a problem if HEAD is gone23:27
clarkbit should generally be fine23:27
pabelangerHEAD should be master in this case23:27
clarkbbut changes to HEAD don't propogate23:27
clarkbpabelanger: I understand refs/remotes/origin/HEAD will become danglin as a result of git remote prune means "if I delete the branches you've asked me to delete then refs/remotes/origin/HEAD will pointto a branch that does not exist anymore"23:28
pabelangeryah, I'm just surprised that HEAD was not master23:29
pabelangerI need to go back and look23:30
pabelangerin this case, it was just a random branch that developer created to create a PR from23:30
*** jamesmcarthur has quit IRC23:32
*** mattw4 has quit IRC23:37
*** jamesmcarthur has joined #zuul23:38
*** jamesmcarthur has quit IRC23:42

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