Thursday, 2018-03-22

*** odyssey4me has quit IRC00:02
*** odyssey4me has joined #zuul00:03
*** rlandy has quit IRC00:03
dmsimardcorvus: would it be appropriate to install the mysql-client package on the zuul scheduler node in puppet-zuul ? I wanted to check something but it's not installed :(00:19
clarkbif we want to do backups of that db we probably want those tools too00:19
dmsimardhow are database backups done today ? is that automated by trove ?00:25
clarkbno, we use mysql dump to the local host then bup backs those files up to the bup server00:27
dmsimardso I guess that's broken right now then00:27
* dmsimard looks00:27
clarkbone of the goals there was to preserve append only backups like we have with the rest of our backups00:28
dmsimardI know the zuulv3 node had it because I remember using it once00:28
dmsimardso we lost it with the change to zuul0100:28
clarkbI'm not sure we ever had backups for it though00:28
corvusdmsimard, clarkb: let's bmove to #openstack-infra00:39
dmsimardcorvus: how about we send the puppet-zuul gerritbot notifications here ?00:52
*** JasonCL_ has joined #zuul00:56
*** JasonCL has quit IRC00:58
openstackgerritIan Wienand proposed openstack-infra/nodepool master: [WIP] Test growroot in boot tests  https://review.openstack.org/55510300:59
corvusdmsimard: right now, i'd rather not.  i'm unaware of anyone not openstack-related using it.01:05
dmsimardThat's why I figured I should ask first, thanks for confirming :D01:05
*** harlowja has quit IRC01:31
*** dtruong2 has joined #zuul02:09
*** dtruong2 has quit IRC02:29
*** harlowja has joined #zuul03:32
*** harlowja has quit IRC03:54
openstackgerritIan Wienand proposed openstack-infra/nodepool master: [WIP] Test growroot in boot tests  https://review.openstack.org/55510304:07
*** persia has quit IRC04:13
*** persia has joined #zuul04:14
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: add a job build button  https://review.openstack.org/55483905:36
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: job-trigger: add initial driver and event  https://review.openstack.org/55515305:36
*** JasonCL has joined #zuul05:40
*** JasonCL_ has quit IRC05:44
*** threestrands has quit IRC06:25
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: job-trigger: add initial driver and event  https://review.openstack.org/55515307:39
*** Wei_Liu1 has joined #zuul07:46
*** Wei_Liu has quit IRC07:46
*** Wei_Liu1 is now known as Wei_Liu07:46
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Clarify position of depends-on footer  https://review.openstack.org/55518507:53
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Clarify location of depends-on footer  https://review.openstack.org/55518507:53
tobiashfixes doc bug ^07:56
*** flepied_ has joined #zuul08:22
*** snapiri has joined #zuul08:25
*** flepied_ has quit IRC08:31
*** electrofelix has joined #zuul08:35
*** yolanda_ is now known as yolanda08:35
*** JasonCL has quit IRC08:38
*** jpena|off is now known as jpena08:48
*** flepied_ has joined #zuul08:58
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: job-trigger: add initial driver and event  https://review.openstack.org/55515309:15
tobiashdoes someone already use nodepool with boot-from-volume?09:18
tobiashhttps://docs.openstack.org/infra/nodepool/configuration.html#pool-labels09:18
*** jesusaur has quit IRC09:20
openstackgerritIan Wienand proposed openstack-infra/nodepool master: [WIP] Test growroot in boot tests  https://review.openstack.org/55510309:24
*** jesusaur has joined #zuul09:28
openstackgerritBernd Bausch proposed openstack-infra/zuul master: Add port to webhook URL in Zuul github driver docu  https://review.openstack.org/55522509:47
openstackgerritBernd Bausch proposed openstack-infra/zuul master: Add port to webhook URL in Zuul github driver docu  https://review.openstack.org/55522509:52
*** hashar has joined #zuul09:58
tristanCtobiash: we did use this option with nodepool-v2 on review.rdoproject.org09:59
openstackgerritTristan Cacqueray proposed openstack-infra/zuul master: web: add a job build button  https://review.openstack.org/55483910:00
tobiashtristanC: ah cool, so I hope it's reliable in deleting the volumes together with the nodes :)10:00
tristanCtobiash: it should as it set the terminate_volume create server option10:01
tobiashah cool10:01
*** sshnaidm has quit IRC11:00
*** jesusaur has quit IRC11:02
*** logan- has quit IRC11:03
*** logan- has joined #zuul11:03
*** jesusaur has joined #zuul11:12
openstackgerritMerged openstack-infra/zuul master: Add port to webhook URL in Zuul github driver docu  https://review.openstack.org/55522511:12
mordredtristanC, tobiash: we actually just rolled a use of boot-from-volume in nodepool live in infra for vexxhost11:15
tobiash:)11:16
mordredthey're a ceph cloud, so boot-from-volume + uploading raw images means _very_ inexpensive/quick boot times11:16
tobiashmy use case is support for larger disks than the flavor11:16
mordredtobiash: good use case11:16
tobiashyah that's cool, our cloud is also ceph only11:16
openstackgerritIan Wienand proposed openstack-infra/nodepool master: [WIP] Test growroot in boot tests  https://review.openstack.org/55510311:21
*** odyssey4me has quit IRC12:07
*** odyssey4me has joined #zuul12:08
*** sshnaidm has joined #zuul12:25
*** rlandy has joined #zuul12:29
kklimondahmm, any idea how to debug error "SSH Error: data could not be sent to remote host X. Make sure this host can be reached over ssh" when using add-fileserver and upload-logs ? The logserver only logs the following in auth.log: "Did not receive identification string from 192.168.0.5"12:34
kklimondait's failing on "[upload-logs : Create log directories]"12:35
tobiashkklimonda: plain ssh with -vvv helps often12:49
kklimondatobiash: can I somehow force ansible to use -vvv for ssh and print output?12:51
tobiashkklimonda: you can switch the executor into verbose mode12:52
tobiash'zuul-executor verbose'12:52
tobiashthen you find these logs in the debug logging12:52
kklimondayes, I was running executor with verbose already - that did not display connection info, but that's because we don't add enough -v's12:56
kklimondawell, that doesn't actually print anything more :/12:58
*** electrofelix has quit IRC12:58
Shrewsprotip: Do not attempt to use devstack with nodepool. Use the static driver b/c OMGSOMUCHEASIER13:01
*** dkranz has joined #zuul13:02
kklimondaall I get is this measly log http://paste.openstack.org/show/708949/13:02
*** JasonCL has joined #zuul13:18
*** sshnaidm has quit IRC13:19
*** sshnaidm has joined #zuul13:20
*** dmsimard has quit IRC13:21
*** JasonCL has quit IRC13:23
*** JasonCL has joined #zuul13:24
*** JasonCL has quit IRC13:28
*** JasonCL has joined #zuul13:32
*** dmsimard has joined #zuul13:34
kklimondalooks like I've managed to run my zuul-executor as root and that broke things? I saw a weird error when trying to ssh to the logserver from an ansible task: http://paste.openstack.org/show/708955/13:42
*** JasonCL has quit IRC13:45
*** JasonCL has joined #zuul13:54
*** JasonCL has quit IRC14:08
*** JasonCL has joined #zuul14:09
*** JasonCL has quit IRC14:24
*** JasonCL has joined #zuul14:26
*** JasonCL has quit IRC14:35
*** JasonCL has joined #zuul14:37
*** JasonCL has quit IRC14:39
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Add autohold debug info  https://review.openstack.org/55532714:53
*** JasonCL has joined #zuul14:57
*** JasonCL has quit IRC14:58
*** JasonCL has joined #zuul14:58
*** swest has quit IRC15:10
*** hashar is now known as hasharAway15:13
Shrewscorvus: did you mean to output the autohold debug line when the key is None?15:21
Shrewsi guess knowing if None is returned could be useful there15:22
corvusShrews: yes, that's it exactly15:23
*** JasonCL has quit IRC15:35
*** JasonCL has joined #zuul15:36
pabelangerkklimonda: how did your executor start as root? Left over from the time when the executor would drop permissions to bind to finger port?15:37
kklimondapabelanger: yeah, I have my own systemd scripts used in another deployment and that deployment hasn't been uploaded in a while15:39
pabelangerack15:39
*** JasonCL has quit IRC15:44
openstackgerritMerged openstack-infra/zuul master: Add autohold debug info  https://review.openstack.org/55532715:44
*** JasonCL has joined #zuul15:45
*** JasonCL has quit IRC15:46
*** JasonCL has joined #zuul15:46
*** harlowja has joined #zuul16:04
*** JasonCL has quit IRC16:06
*** JasonCL has joined #zuul16:07
*** harlowja has quit IRC16:09
*** rlandy is now known as rlandy|biab16:36
*** sshnaidm is now known as sshnaidm|off16:38
pabelangerquestion about private clouds and nodepool / zuul.  I know today zuul-executor would need to be able to access the private IP, but with nodepool-launcher assuming openstack APIs are public and don't want a public ip address for nodes, I still think nodepool-launcher needs to be on private network, since we ssh-keyscan for hostkeys. Thoughts on how we could maybe fix that and only have zuul-executor on private16:56
pabelangernetwork?16:56
clarkbpabelanger: we talked about this at the ptg as it is a need for rcarrillocruz and mrhillsman16:59
clarkbpabelanger: basically you'd run zuul-executor and nodepool launcher (possibly builder too) in the private portion of the cloud and punch holes for them to talk to control plane17:00
pabelangeryah, that's what I was hoping. Don't think I was in the room during that time17:00
clarkbthen the major missing piece is executor affinity to cloud resources17:00
clarkbthe PTG etherpad has a link to a story on how to do ^17:00
*** tosky has joined #zuul17:00
pabelangerclarkb: right, in this case, the cloud is public, but doesn't have enough FIPs for ipv4 or ipv6. So, openstack APIs would be on public network, only traffic from zuul-executor would need to be private.17:01
pabelangerI think if we disabled ssh-keyscan in nodepool-launcher, that  too could be public17:01
mrhillsmani started back testing this with the request to try out zuul from scratch17:01
pabelangerand / or move that to executor17:01
mrhillsmani have not got a job to run yet but will probably test it today17:01
mrhillsmanright now i keep nodepool-launcher/builder and zuul-executor inside of the cloud via openstack VMs17:02
mrhillsmaneverything else is in the public space17:02
mrhillsmanright now they can all talk17:02
mrhillsmanjust need to confirm job execution happens17:02
pabelangeryah, I'd like to keep nodepool bits public, since they could also work on another cloud, over installing additional services17:03
clarkbmrhillsman: ya then if you have a mixed env you just need to specify "these labels can only be reached by this executor" and there is a detailed story on making that change to zuul17:03
mrhillsmanyep17:03
pabelangerbut agree zuul-executor would need to be private17:03
mrhillsmanhow would that work though pabelanger17:03
pabelangerif only nova gave us hostkeys for nodes :)17:03
mrhillsmansince nodepool has to talk to the cloud17:04
pabelangermrhillsman: cloud is public17:04
pabelangerbut doesn't have enough public ips for VMs17:04
clarkbright separation of cloud api and cloud resources17:04
pabelangeryah17:04
clarkbthe cloud api is public, the resources are not17:04
pabelangerexactly17:04
mrhillsmanoh ok17:04
mrhillsmani have the case of both being private :)17:04
mrhillsmanso an executor in the private cloud does not facilitate that?17:05
pabelangerin fact, I think this could be tested in the gate via nodepool dsvm job, and a little hacking17:05
clarkbmrhillsman: it does, pabelanger is talking about trying to make the nodepool launcher not private17:06
pabelangermrhillsman: no, I think that is the one item that needs to be in private17:06
pabelangerthe only thing nodepool-launcher does to a node now is ssh-keyscan it for hostkeys, because we have no other way to get that info, so it would need routing access to private network17:06
clarkbpabelanger: my concern with moving that out of the nodepool launcher is that even though openstack can't do it today other compute resource platforms may be able to provide those host keys to nodepool in which case you would not want to set it up in the fashion you describe because you would be lowering your level of security17:06
pabelangerif we make that optional and move into executor, that would fix that17:06
corvus17:05 < openstackgerrit> James E. Blair proposed openstack-infra/project-config master: Add publish-zuul-docs job  https://review.openstack.org/55537717:06
corvus^ that is a step to get zuul docs published to zuul-ci.org/docs/zuul17:07
clarkbpabelanger: I'm somewhat inclined to say you should just run a private launcher for this reason too17:07
clarkb(I don't actually knwo if any other platforms support that though)17:07
pabelangercorvus: clarkb: right, I think that is completely reasonable to say. But, does mean more overhead on operator to support.17:08
clarkbpabelanger: ya but so is using complicated private resources17:08
corvusi believe rcarrillocruz has a patch in progress for executor affinity (we'll land it after 3.0)17:08
clarkbits complicated not because of nodepool but because of your operating environment17:08
corvusmaybe we could make it a switch?17:09
mrhillsmanlauncher does not use much of anything so if one has executor inside private network how much more would it require to co-locate launcher17:09
clarkbcorvus: ya secure (or in openstack case best effort) by default then opt in if people don't care?17:10
pabelangerkeyscan a switch?17:10
corvusclarkb, pabelanger: yes17:10
clarkbif your executor is in the private env already it is likely that your chances for a mitm attack are lowered17:10
clarkbmrhillsman: I think its more about needing a one off launcher just for that cloud. If you are talking to many clouds that is annoying17:10
clarkbmrhillsman: if it is your only cloud it makes no difference17:10
pabelangeryah, I'd be okay with that17:10
corvusright, ^ this is a case where the right answer may be topology dependent, so a switch may not be unreasonable.17:11
mrhillsmantrue, makes sense17:11
mrhillsmanbut if you are using windmill :)17:11
pabelangercool, I'll hack on it after 3.0 release :D17:12
mrhillsmanjust a little joke there17:12
mrhillsmani am still learning things but would be cool to have a switch17:12
pabelangerwell, this is actually for testing with RDO cloud, they have limited public IPs ATM17:12
clarkbpabelanger: another important thing to keep in mind is that public vs private is really not the correct terminology17:13
clarkbpabelanger: the IPs need to be reachable from the executor and the launcher. In a corporate env or a single cloud that may mean everyone is "private" but its "public" to the serivces17:14
mrhillsmanyeah i think i am getting confused as well by that and my lack of knowing how things work17:14
clarkbpabelanger: so if your launcher was running in the rdo cloud it could talk to rdo cloud resources and other public clouds just fine17:14
clarkbpabelanger: without changing anything (potentially depending on network topology, terms and conditions apply)17:14
mrhillsmanno total lack of course17:14
mrhillsmans/no/not17:14
pabelangerclarkb: yah17:15
mrhillsmanwe do that right now but i do not think it scales as mentioned17:15
clarkbmrhillsman: it would scale as long as the other clouds were also accessible from there17:15
clarkbmrhillsman: possibly because they are true public clouds and the launcher can talk to them via NAT out of its private env or bceause its another cloud on the same private corp networking env17:15
mrhillsmanwe have limited public IPs so we do not attach public IPs to the launched VMs17:15
pabelangerclarkb: you summed it up right with: the cloud api is public, the resources are not17:16
clarkbmrhillsman: right but they don't have to be true public clouds, they just have to be "public" or rather reachable from the services17:16
mrhillsmanyeah, all the services are running within that cloud17:16
mrhillsmanand all the other clouds are public17:16
mrhillsmanthis conversation probably sheds some light on why our initial cloud behind VPN stuff was not working17:17
mrhillsmanthis was actually quite timely for me and gives me a little bit more to chew on with re to what we are doing17:19
clarkbfor example if I was still at HP we had ssh access out of the corporate network. So I could run all my control plane in the "private" corp env against our internal cloud using privately IP'd instances. Then also talk to a true public cloud using public IPs from my control plane in private land17:19
clarkb(this particular use case helped inform a bit of the new zuulv3 and nodepool design aiui)17:19
mrhillsmanwas your control plane in the corp env running in the internal cloud?17:20
clarkbit was running on the precursor to the internal cloud, a vmware cluster17:21
mrhillsmanok, i am running everything in the internal cloud17:22
mrhillsmani hope things work but at least i have a bit more understanding now on this front and can probably ask better questions going forward17:22
mrhillsmanit was a lot easier to get setup again and fix issues versus some months ago for sure17:23
pabelangerclarkb: I'm actually checking now to see if current setup of nodepool-launcher is on same private network as VMs today. Don't have direct access myself17:24
clarkbpabelanger: it doesn't have to be on the same network either, just be able to route to it17:24
pabelangerright17:25
clarkbzuulv2 required that instance be able to reach back to the control plane which is trickier in corporate envs if consuming public compute resources (or any other less trusted compute resource)17:26
clarkbwhich is why zuulv3 is so push heavy (git repos are pushed, it sshes to instances, etc)17:27
*** rlandy|biab is now known as rlandy17:40
*** tosky has quit IRC17:44
*** tosky has joined #zuul17:48
Shrewsour zuul setup guides don't mention anything about gerrit setup. should it? any special steps one needs to take for that?17:53
clarkbShrews: you need a gerrit user with the stream ssh events right in gerrit (it is an acl now) then you configure zuul to use that user and ssh key17:55
clarkbits probably something that should be included at some point17:55
corvusyeah, i'd like to branch the zuul-from-scratch guide so we have a github/gerrit path.  choose your own adventure17:56
*** flepied_ has quit IRC17:57
openstackgerritJames E. Blair proposed openstack-infra/zuul master: Publish zuul docs to zuul-ci.org  https://review.openstack.org/55539517:58
corvusif folks could approve that, i can verify/fix the new docs publishing job, and then we can add it to the other repos17:59
*** jpena is now known as jpena|off18:00
mordredcorvus: ++18:02
Shrewscorvus: ++  I'm attempting to setup things on my local machine and kind of hit that roadblock18:03
corvusShrews: cool, if you end up going the gerrit route and record your process, we could incorporate it into the docs18:06
Shrewscorvus: sure... assuming i can figure out the process :)18:06
*** harlowja has joined #zuul18:15
*** harlowja_ has joined #zuul18:17
*** harlowja has quit IRC18:19
*** flepied_ has joined #zuul18:35
openstackgerritMerged openstack-infra/zuul master: Publish zuul docs to zuul-ci.org  https://review.openstack.org/55539518:41
*** JasonCL has quit IRC18:44
*** JasonCL has joined #zuul18:50
*** JasonCL has quit IRC18:51
*** JasonCL has joined #zuul19:01
*** JasonCL has quit IRC19:05
Shrewscorvus: standard gerrit setup doesn't seem to match our normal workflow (no +/-W buttons present). Do we want to recommend a particular configuration?19:21
Shrewsoh, maybe that's b/c i'm the admin user19:22
clarkboh right they only use code review by default now19:22
Shrewsyeah, i'm running with the latest19:22
Shrews2.14.6 iirc19:23
Shrews2.14.719:23
Shrewsi guess we aren't version restricted, right?19:23
tobiashShrews: yes, default is without workflow and verified only between -1 and 119:24
tobiashbut I guess if the target is gating then at least verified needs to be -2 to 219:24
tobiashworkflow might be optional19:24
Shrewsi need to figure out the proper config settings then  :/19:25
*** trishnag has joined #zuul19:25
clarkbits pretty straightforward we probably have examples in the spec repo configs19:26
trishnagHi, is there a way that I can get an offline version of zuul doc https://docs.openstack.org/infra/zuul?19:27
Shrewsclarkb: yeah, trying to parse http://git.openstack.org/cgit/openstack-infra/puppet-gerrit/tree/templates/gerrit.config.erb atm19:27
Shrewsbut if they've recently changed the default, we probably aren't using the config value yet19:28
tobiashShrews: we have something like this in the project config: http://paste.openstack.org/show/708994/19:29
clarkbShrews: we override the default iirc19:30
clarkbShrews: so that we have the extra stuff19:30
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Add missing localhost delegation checks to some modules  https://review.openstack.org/55543519:30
corvusShrews: we actually don't go into gating for github either yet; it might be worth just sticking with 'check' for starters, then adding 'gate' later19:31
*** robled has quit IRC19:31
tobiashcorvus, mordred, clarkb: ^19:31
Shrewscorvus: good point19:32
tobiashI think without gating the default settings (except permissions) should be ok19:32
clarkbtobiash: corvus I realize the commit message about the whitelist is a little stale now19:35
clarkbtobiash: corvus but I don't know that that is important enough to change at this point?19:36
tobiashups19:36
tobiashoverlooked that19:36
tobiashjust a sec19:36
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Add missing localhost delegation checks to some modules  https://review.openstack.org/55543519:37
clarkbI guess its good for breadcrumbs in the future to get that right19:37
corvustrishnag: you can locally generate an html version (just run 'tox -e docs').  or it should be possible to build a pdf, though i haven't tried it and am not sure how well it will turn out.19:37
*** patriciadomin has quit IRC19:38
clarkbtobiash: noticed somethign else linting may care about but if it doesn't then lets just merge it as is and clean it up later19:39
tobiashclarkb: I thought I ran pep8 locally19:40
clarkbtobiash: its possible top level unused vars like that are treated differently because they are global19:40
openstackgerritTobias Henkel proposed openstack-infra/zuul master: Add missing localhost delegation checks to some modules  https://review.openstack.org/55543519:42
clarkbsorry, its just things like that are easier to notice in gerrit :)19:44
tobiashno problem, it's easy to fix :)19:44
*** rlandy is now known as rlandy|brb19:54
*** robled has joined #zuul20:07
openstackgerritMerged openstack-infra/zuul master: Add missing localhost delegation checks to some modules  https://review.openstack.org/55543520:20
tobiash\o/20:20
tobiashthat should be the last of the current sec fixes20:21
tobiashcorvus, clarkb, fungi: https://etherpad.openstack.org/p/IMSdAnUVuN20:21
pabelangertobiash: awesome work increasing our testing around ansible!  Great to see.20:23
tobiashthanks :)20:24
clarkbtobiash: lgtm20:26
pabelangerwfm, added trivial update20:27
trishnagcorvus: thanks20:27
*** rlandy|brb is now known as rlandy20:30
*** flepied_ has quit IRC20:33
*** flepied has joined #zuul20:33
fungitobiash: advisory looks great, thanks!20:39
*** JasonCL has joined #zuul21:04
clarkbhttp://zuul.openstack.org/stream.html?uuid=a363be3162ab4ce0b4f0df527a004a78&logfile=console.log says Failure from finger client: host and port was not specified and no sock specified should i be worriedabout that post executor restart?21:09
*** flepied has quit IRC21:10
clarkbhrm now it shows up21:12
tobiashclarkb: I also see this in my deployment21:13
clarkbtobiash: some kind of delay in starting the socket maybe?21:14
tobiashIt looks like the streamink link is shown too early21:14
pabelangerclarkb: yah, think there is a race21:14
pabelangerI think if merger on executor is delayed, it happens21:14
pabelangermaybe we should only update webui after local repos are setup21:15
tobiashAt some point the executor reports a url back to the scheduler an I think there was a change a while ago to report that later21:17
tobiashBut it still might be too early21:18
tobiashpabelanger, clarkb: that updates the link: http://git.openstack.org/cgit/openstack-infra/zuul/tree/zuul/executor/server.py#n75721:24
clarkband that happens before run playbooks is called21:25
tobiashYa21:25
clarkbhttp://git.openstack.org/cgit/openstack-infra/zuul/tree/zuul/executor/server.py#n880 is maybe a better place to call it?21:25
tobiashProbably21:27
*** JasonCL has quit IRC21:33
*** JasonCL has joined #zuul21:34
*** JasonCL has quit IRC21:36
*** JasonCL has joined #zuul21:43
*** JasonCL has quit IRC21:47
pabelanger++21:58
*** JasonCL has joined #zuul22:01
*** rlandy is now known as rlandy|bbl22:04
*** JasonCL has quit IRC22:08
*** JasonCL has joined #zuul22:41
*** JasonCL has quit IRC22:42
corvushttps://zuul-ci.org/docs/zuul/22:46
corvuswow that worked the first time :)22:46
Diabelkohi, I'm having an issue where Zuul suddenly started saying that change is not ready to be merged and ignoring the review22:50
Diabelkoparent of the commit is merged, there's everything in place22:50
DiabelkoI can give links to gerrit/code/logs, anything really22:51
Diabelkobut I have no idea what the issue might be22:51
Diabelkoparent is merged, this is a revert commit22:51
corvusDiabelko: a link to the change would help.  and do you have zuul debug-level logs?22:53
Diabelkoyes, I do22:54
Diabelkocorvus: https://review.opencontrail.org/#/c/40958/ this is a review that refused to run, https://review.opencontrail.org/#/c/40570/2 this one otoh, for the same repo, runs just fine22:55
Diabelkohttp://zuulv3.opencontrail.org22:55
Diabelkocontrail-project-config is our repo with zuul configuration and ansible code22:56
Diabelkohttps://review.opencontrail.org/#/c/40970/ and this is duplicated 40958, because I wanted to see what's happening22:57
corvusDiabelko: can you paste the logs starting at "Considering adding change .* 40958"22:57
corvusexample: 2018-03-22 06:28:18,247 DEBUG zuul.Pipeline.openstack.gate: Considering adding change <Change 0x7f79792ecef0 555152,1>22:58
openstackgerritIan Wienand proposed openstack-infra/nodepool master: Test growroot in boot tests  https://review.openstack.org/55510323:00
openstackgerritJames E. Blair proposed openstack-infra/nodepool master: Publish docs to zuul-ci.org  https://review.openstack.org/55549723:06
openstackgerritJames E. Blair proposed openstack-infra/zuul-sphinx master: Publish docs to zuul-ci.org  https://review.openstack.org/55550123:09
Diabelkomhm, sure23:09
openstackgerritJames E. Blair proposed openstack-infra/zuul-sphinx master: Publish docs to zuul-ci.org  https://review.openstack.org/55550123:11
Diabelkocorvus: http://paste.openstack.org/show/709119/23:11
corvusDiabelko: ok it added it to the queue.  but it must have later removed it without reporting.23:14
corvusDiabelko: what other log lines are there for 40958,2 after that?23:14
Diabelkocorvus: I don't see anything apart from that, let me run recheck again for that23:21
Diabelkocorvus: http://paste.openstack.org/show/709140/ saw something new23:23
Diabelko"No jobs for change <Change 0x7f0704a27898 40958,3>"23:23
clarkbI'm assuming that is a trusted config project? which would mean that noop jobs addition wouldn't apply until it merges23:24
clarkbthat leaves you with the lint jobs that we would expect to run right?23:24
Diabelkoyes23:24
Diabelkoto both yes23:25
DiabelkoI can open another review with different content, but with the same commit id as parent23:25
Diabelkoand we can see if it happens23:25
corvusDiabelko: zuul-jobs-linters has a files restriction: https://github.com/Juniper/contrail-zuul-jobs/blob/master/zuul.d/infra-jobs.yaml#L8623:26
corvusDiabelko: and since it doesn't match, there are in fact no jobs to run on that change23:26
Diabelkohttps://review.opencontrail.org/#/c/40946/23:29
Diabelkowhile I can see what you mean, I have no idea why it worked before then23:30
clarkbcould be a newer restriction?23:33
corvusyeah, was added 3 days ago: https://github.com/Juniper/contrail-zuul-jobs/commit/0cdbfdd4ac067ea037056aed892567d8c920215d23:33
*** JasonCL has joined #zuul23:33
corvuser, actually, it looks like that commit merged today23:34
corvusDiabelko: https://review.opencontrail.org/#/c/40820/23:34
*** JasonCL has quit IRC23:34
Diabelkoah!23:34
DiabelkoI was sure it was added 3 days ago23:35
Diabelkothank you for that guys... MVPs!23:35
Diabelko:)23:35
corvusDiabelko: no prob!23:35
Diabelkoand I am so sorry for bothering you with stuff like that :(23:35
clarkbI think there is a bug about logging this case right?23:36
Diabelkokklimonda: ^ FYI it's your fault :>23:38
Diabelkothank you guys again23:38
*** tosky has quit IRC23:43
openstackgerritJames E. Blair proposed openstack-infra/zuul-website master: Add a documentation index page  https://review.openstack.org/55550523:51
*** xinliang has quit IRC23:58
*** JasonCL has joined #zuul23:59

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