Tuesday, 2018-10-30

openstackgerritMerged openstack-infra/zuul-jobs master: Fix noqa warning  https://review.openstack.org/61378500:10
*** dmsimard has quit IRC00:28
openstackgerritMerged openstack-infra/nodepool master: Cleanup down ports  https://review.openstack.org/60982901:12
*** bhavikdbavishi has joined #zuul01:36
*** bhavikdbavishi has quit IRC02:08
*** rcarrillocruz has quit IRC02:43
*** bhavikdbavishi has joined #zuul03:11
*** pwhalen has joined #zuul03:13
*** dmsimard has joined #zuul04:27
*** dmsimard has quit IRC04:45
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Logs stats for nodepool automated cleanup  https://review.openstack.org/61407404:57
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Logs stats for nodepool automated cleanup  https://review.openstack.org/61407405:01
*** dmsimard has joined #zuul05:10
tobiashclarkb, mordred: https://review.openstack.org/613674 looks tailored a bit to the openstack ecosystem. Shall this really be part of zuul or rather live in project-config?05:16
clarkbtobiash ya I think everything but that is generally useful05:19
clarkband if we assume a generic grouping method we could maybe feed in a "projects" file that isnt openstack specific?05:20
clarkbfwiw it totally works if that file isnt present but the output may say too mamy openstacks05:20
clarkbfeel free to -1 and I'll see if I can clean it up to be more general05:20
clarkbmostly I think zuul needs something like that for people to better understand usage and the openstack bits can be cleaned up05:23
tristanCclarkb: it seems like we could build such report from the build endpoint instead, but it is still missing nodeset information05:28
clarkbtristanC: correct. This was a quicker easy step that corvus pushed up05:29
tobiashclarkb: yes, I'd really like that to have in zuul, I just stumbled over the openstackiness ;)05:29
tristanCanother informations that may be useful is the nodesets/labels used by each project05:32
tobiashclarkb: I'm fine feeding in a projects file as a followup. Regarding the openstack comment, I think this can be cleaned up quickly :)05:36
*** pcaruana has joined #zuul05:36
tobiashclarkb: a further think I stumbled accross is that this script makes a difference between project and repo where zuul itself uses these terms as synonyms05:37
tobiashthis can be quite confusing and might need more explanation in the script05:37
clarkbyes I even stumbled over that myself abit if you look at older patchsets. Basically tries to show a differemce between logical collections of wokr and repo specific work05:41
*** pcaruana has quit IRC05:47
*** mnaser has quit IRC06:16
*** mnaser has joined #zuul06:17
*** smyers has quit IRC06:18
*** smyers has joined #zuul06:18
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: WIP: Add request handler timer to stats  https://review.openstack.org/61407906:31
tobiashShrews, ianw, corvus: what do you think about this metric? ^06:31
tobiashif you think that is valuable I'll add documentation and release notes06:31
*** quiquell|off is now known as quiquell06:34
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Logs stats for nodepool automated cleanup  https://review.openstack.org/61407407:17
ianwtobiash: lgtm07:23
tobiash:)07:23
*** themroc has joined #zuul07:43
*** pcaruana has joined #zuul07:57
*** pcaruana is now known as pcaruana|elisa|07:59
*** quiquell has quit IRC08:12
*** jpena|off is now known as jpena08:57
*** sshnaidm|bbl is now known as sshnaidm|off09:02
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: WIP: Add request handler timer to stats  https://review.openstack.org/61407909:19
*** hashar has joined #zuul09:26
*** bhavikdbavishi has quit IRC10:20
*** electrofelix has joined #zuul11:04
*** bhavikdbavishi has joined #zuul11:14
*** nilashishc has joined #zuul11:22
*** hashar is now known as hasharLunch11:28
*** bhavikdbavishi has quit IRC11:35
tobiashShrews, corvus: the cleanup ports feature in nodepool had severe side effects in our production environment. It cleaned up *all* ports regardless of the state. (maybe the reported state of the cloud was wrong)11:38
tobiashShrews: corvus: I think we need to make this optional and disabled by default11:38
*** bhavikdbavishi has joined #zuul11:41
*** jesusaur has quit IRC11:56
*** jpena is now known as jpena|lunch11:57
*** jesusaur has joined #zuul12:01
*** bhavikdbavishi has quit IRC12:07
tobiashShrews: corvus: mordred: when running the port list the filters don't work: https://git.zuul-ci.org/cgit/nodepool/tree/nodepool/driver/openstack/provider.py#n43212:13
*** jesusaur has quit IRC12:13
openstackgerritTobias Henkel proposed openstack-infra/nodepool master: Revert "Cleanup down ports"  https://review.openstack.org/61419812:14
tobiashShrews, mordred, corvus: I don't know if you want to fix forward or first revert that patch so here is the revert. Feel free to ignore if you see the problem and want a fix instead ^12:15
tobiashmordred: how are the filters intended to use in list_ports of openstacksdk?12:23
tobiashlocal testing shows that this has no effect12:24
tobiashmordred: it seems to be a bug in openstacksdk12:27
tobiashmordred: 'port = cloud._list_ports({'status': 'DOWN'})' works12:28
tobiashmordred: while 'port = cloud.list_ports(filters={'status': 'DOWN'})' ignores the filter12:28
tobiashmordred: I suspect the problem is here: http://git.openstack.org/cgit/openstack/openstacksdk/tree/openstack/cloud/openstackcloud.py#n170612:29
*** rlandy has joined #zuul12:35
*** bhavikdbavishi has joined #zuul12:39
*** jesusaur has joined #zuul12:41
jheskethmordred, clarkb: I've made some progress on the API and tooling required for running local jobs. I pushed this up before I left on vacation for most of October. I'm back as of this week and will be resuming work on it: https://review.openstack.org/#/q/status:open+project:openstack-infra/zuul+branch:master+topic:freeze_job12:54
tobiashinfra-root: just to be sure: the port cleanup problem was *not* caused by my cloud but by a bug in openstacksdk. Thus you should not update your nodepool-launchers until this problem is fixed.12:58
fungithanks for the heads up tobiash!12:59
fungitobiash: do you have a link to the openstacksdk story with details?12:59
tobiashthere is no story yet12:59
tobiashjust a code pointer to mordred 20 lines up in the backlog ;)12:59
tobiashfungi: I'll create a story13:01
*** hasharLunch is now known as hashar13:01
fungithat line was last changed 2016-08-3013:03
tobiashfungi: that might have something to do with caching13:05
fungibut yeah, definitely looks like it clears all filters passed to the method if the first conditional doesn't match13:05
tobiashfungi, mordred: story for openstacksdk: https://storyboard.openstack.org/#!/story/200420713:06
*** jpena|lunch is now known as jpena13:12
tobiashfungi: you seem to use the same caching so it's likely that openstack-infra would run into the same issue13:12
*** bhavikdbavishi has quit IRC13:12
Shrewstobiash: eek. i think we should revert, then we can add it back later with updated requirements13:27
mordredtobiash: oh sigh13:28
Shrewstis a silly bug13:28
Shrewstobiash: but kudos for trying it in production!  :)13:29
Shrewsmordred: fungi: one of you care to +3 that revert (https://review.openstack.org/614198)?13:34
mordreddone13:35
mordredShrews: I'm working on sdk fix13:36
Shrewsmordred: cool thx. is it possible to create ports in the DOWN state? would be good to have a func test for that13:38
mordredShrews: I do not know. we could try being evil and just editing the neutron database behind the scenes...13:38
* Shrews checks api guide13:38
mordredy13:40
mordredgah13:40
Shrewsnot seeing a way to do it13:41
mordredShrews: https://review.openstack.org/614213 Filter ports in list_ports when batching is in effect13:42
Shrewsmordred: i dont think filters=None is going to work in _filter_list13:45
mordredno? do we need to pass it a {}?13:45
Shrewsmordred: oh, nm. it will13:45
Shrewsif not filters: return data13:45
Shrewscool13:45
mordredoh cool13:46
mordredyay! it's almost like we thought of something13:46
openstackgerritMerged openstack-infra/nodepool master: Revert "Cleanup down ports"  https://review.openstack.org/61419814:04
*** nilashishc has quit IRC14:21
*** pcaruana|elisa| has quit IRC14:33
mordredtobiash: https://review.openstack.org/#/c/614213 I believe should fix the error you hit14:41
tobiashmordred: thanks14:42
tobiashmordred: thank god my nodepool was operating in a separate tenant14:44
tobiashmordred: in my dev environment this is not the case. That would have committed suicide...14:44
*** pcaruana|elisa| has joined #zuul14:45
mordredtobiash: yah - it's a really bad bug ... I'm *VERY* glad it didn't cause more damage14:45
tobiashwell, it killed 300 jobs...14:45
tobiashbut it was just jobs14:46
tobiashso could have been worse14:46
mordred++14:46
openstackgerritBenoĆ®t Bayszczak proposed openstack-infra/zuul master: Disable Nodepool nodes lock for SKIPPED jobs  https://review.openstack.org/61326114:47
Shrewstobiash: sorry for the mess14:47
tobiashShrews: that wasn't foreseeable14:48
tobiashShrews: and in fact I approved this change ;)14:49
*** bbayszczak has joined #zuul14:52
*** ianychoi_ is now known as ianychoi15:07
*** nilashishc has joined #zuul15:10
*** swest has quit IRC15:18
*** pcaruana|elisa| has quit IRC15:35
*** pcaruana|elisa| has joined #zuul15:50
*** pcaruana|elisa| has quit IRC16:00
openstackgerritClark Boylan proposed openstack-infra/zuul master: Small script to scrape Zuul job node usage  https://review.openstack.org/61367416:10
clarkbtobiash: ^ I think that is generally useable by anyone now16:10
clarkbtobiash: can you look it over and make sure I didn't miss anything?16:10
clarkbrather than make it an argument to the script I was thinking just do the right thing if the data is there. But I think current ps still prints the header which may be confusing. Lets not print the header if there is no logical grouping data16:16
openstackgerritClark Boylan proposed openstack-infra/zuul master: Small script to scrape Zuul job node usage  https://review.openstack.org/61367416:18
*** themroc has quit IRC16:41
*** hashar is now known as hasharAway16:55
openstackgerritFabien Boucher proposed openstack-infra/zuul master: WIP - Pagure driver  https://review.openstack.org/60440417:05
*** nilashishc has quit IRC17:21
*** dmsimard has quit IRC17:24
*** panda is now known as panda|off17:37
tobiashclarkb: will look later, out for dinner atm17:44
*** electrofelix has quit IRC17:50
*** bbayszczak has quit IRC17:53
ssbarneai think found a bug in zuul where "files" (include) does not take precedence over "irrelevant-files" (exclude), see https://review.openstack.org/#/c/614242/17:56
ssbarneawhy is this a problem: because it does not allow me to override default excludes from parent by adding explicit includes at lower level.17:57
ssbarneafor example rsync respects this, by applying includes after excludes, not before.17:57
ssbarneaam I wrong?17:57
*** chandankumar is now known as chkumar|off18:05
*** jpena is now known as jpena|off18:10
Shrewsssbarnea: i don't files is supposed to take precedence over irrelevant-files. You can override 'files' from parent jobs, but I don't think using both is recommended.18:19
Shrewsunless we've added a feature i'm not aware of18:20
ssbarneaShrews: i can explain why. At parent I have a long list of ignores, but for specific job i wan to remove two of these ignores and run it. with current implementation i am forced to copy the entire list of ignores form parent to child job.18:21
ssbarneathis means that any change to parent would count as "a bug" in child job, because nobody would ever bother to copyi them to children.18:21
Shrewsyeah, i think you just have to copy the entire list (minus what you don't want)18:21
ssbarneaShrews: you are right, this is the only way to do it now. But if include / excluded would work as mentioned, it could be possible to do it like i described18:22
ssbarneathis is why most of the tools i know that allow for both includes and excludes are following this logic: apply blacklist filter and whilelist after.18:23
Shrewsthat's a feature request (not a bug), and i'm not sure how zuul would know how to handle that18:23
ssbarneaotherwise the include does not really work.18:23
ssbarneayeah it fist the "fug" description, being a bug and a feature, depending how you look at it :D18:24
Shrewsssbarnea: in your example review, how is zuul supposed to know what order to process 'files' and 'irrelevant-files'? Order matters there18:24
ssbarneaam i wrong to assume that ".*" is the implicit behavior?18:25
ssbarneai can write a bug for it with explanation, maybe even find some examples from other tools.18:26
fungissbarnea: you may want to read http://lists.openstack.org/pipermail/openstack-dev/2018-June/131304.html18:26
fungithe present behavior is not the original behavior, and has been discussed at length before settling on it18:26
Shrewsfungi: ah, yes. good memory18:27
fungisuffice to say, a lot of thought has gone into the way it's worknig now18:27
fungithe alternatives have down-sides of their own18:28
ssbarnea... time to block a change before is merged, time to copy/paste config.18:28
ssbarneain fact my case has nothing to do with attribute inheritance, is about documenting the behaviour if a file matches both patterns: files and irrelevant-files.18:30
ssbarneai do not question the lack of merge on inheritance, i can fully understand why this was at least controversial if not really bad.18:30
fungiwe talked about making files and irrelevant-files mutually exclusive, but now i don't remember if that ever happened (i guess it didn't?)18:40
fungii have a feeling part of why files is applied before irrelevant-files is because zuul has to decide whether a job (or variant) is going to be run for a given event so needs to check files if specified, and then can optionally decide not to run based on irrelevant-files?18:44
fungiokay, initial implementation of the current behavior was https://review.openstack.org/57174518:54
fungissbarnea: so is your concern purely over order in which files and irrelevant-files are considered when deciding whether a job is run, or over being forced to replace the lists rather than being able to append to them in a child/variant?18:58
ssbarneafungi: my concern was only about order.18:59
fungii don't think we discussed the former much (other than to say that combining files and irrelevant-files in the same job was a strange choice with undefined results)18:59
ssbarneai find the inheritance behavior ok, expected.18:59
ssbarneain this case i will later file a feature request and document the reasoning. not sure if is easy to implement. i do have a workaround for the moment.19:00
ssbarneaand thanks to everyone for the insights on this.19:00
ianwtobiash: ahh, i think dib functional testing was trying to tell us that the ports thing wasn't working too ... http://logs.openstack.org/47/614047/2/check/nodepool-functional-py35-ubuntu-src/83d0c4e/ara-report/19:21
*** dmsimard has joined #zuul19:23
tobiashouch19:24
*** pcaruana|elisa| has joined #zuul20:12
*** _ari_ has quit IRC20:13
*** pcaruana|elisa| has quit IRC20:32
*** dmsimard has quit IRC21:56
*** dmsimard has joined #zuul22:38
*** pbrobinson has quit IRC22:54
*** pbrobinson has joined #zuul22:59
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Logs stats for nodepool automated cleanup  https://review.openstack.org/61407423:27
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Revert "Revert "Cleanup down ports""  https://review.openstack.org/61437023:27
*** rlandy has quit IRC23:46

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