18:59:50 <SotK> #startmeeting storyboard 18:59:52 <openstack> Meeting started Wed Oct 25 18:59:50 2017 UTC and is due to finish in 60 minutes. The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:59:53 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:59:55 <openstack> The meeting name has been set to 'storyboard' 19:00:11 <SotK> #link https://wiki.openstack.org/wiki/Meetings/StoryBoard#Agenda_for_next_meeting Agenda 19:00:18 <SotK> #topic In Progress Work 19:00:42 <SotK> The database consolidation patch was merged, thank you for the reviews there! 19:00:53 <Zara> thanks for writing it! 19:00:54 <SotK> now hopefully our gate works a bit more smoothly 19:01:13 <SotK> I'd like to fix the test suite more but that is low priority for me now 19:01:16 <Zara> the os testr patch did pass its tests immediately after 19:01:26 <Zara> so that's a good sign 19:01:52 <diablo_rojo> I think I just +1ed it 19:01:56 <Zara> #link https://review.openstack.org/#/c/504525/ 19:02:16 * SotK will review that this evening 19:02:20 <Zara> thanks 19:02:28 <Zara> and thanks mtreinish! :D 19:03:33 <SotK> indeed! 19:03:54 <SotK> the next thing I want to look at is fixing this weird emails bug, but I've not had time to pester anyone about helping this last week or two 19:04:58 <Zara> I've only just got to reviews :/ 19:05:33 <diablo_rojo> SotK, gotta ask for help or else no one will know you need help :) 19:05:45 <SotK> diablo_rojo: I know, but time goes so fast D: 19:06:02 <Zara> I swear it was july last week 19:06:20 <SotK> this matches my perception 19:06:42 <diablo_rojo> Same. 19:06:53 <diablo_rojo> I blinked and three months passed. 19:07:34 <SotK> I should get to rebasing and finishing https://review.openstack.org/#/c/370312/ like I did with the automatic worklists patch soon too 19:07:43 <SotK> one day the teams implementation will be fully featured 19:08:00 <Zara> oh, neat 19:08:05 <diablo_rojo> That day should be soon now that I have proposed this: https://review.openstack.org/#/c/513875/ 19:08:10 <diablo_rojo> A release goal. 19:08:23 <SotK> \o/ thanks diablo_rojo 19:08:31 <Zara> yes, thanks! 19:08:40 <Zara> I've skimmed but not read in depth yet (and feel much guilt about that) 19:08:52 <diablo_rojo> Don't thank me yet- hasn't been merged and once it has we have a lot of work to get done. 19:09:00 <Zara> but you made a thing 19:09:05 <Zara> so you get a thank you 19:09:23 <Zara> it's not the allcaps thank you yet 19:09:33 <Zara> we have tiered thank yous 19:10:26 <Zara> there are also some webclient patches in review that I finally took a look at 19:10:51 <Zara> #link https://review.openstack.org/#/c/511247/ 19:11:09 <Zara> seems fine to me, though I may have missed something subtle 19:11:37 <SotK> seems fine to me too, I'll vote after the meeting 19:11:38 <diablo_rojo> Yeah something is wrong there but I can't see it either. 19:11:47 <Zara> #link https://review.openstack.org/#/c/511246/1 appears to need some reworking to me though if my comment seems misleading or misses some things, feel free to add more 19:12:14 <Zara> our zuul jobs have been doing some strange things and I've put a note in their etherpad for that 19:12:36 <Zara> I was reminded becuase you can see it in the js draft builds for the first of those patches 19:12:47 <Zara> compare the jenkins one to the zuul one 19:12:56 <Zara> well, 'jenkins' 19:13:41 <diablo_rojo> Weird.. 19:13:51 <Zara> aaaand if ever I remember the url for the zuulv3 etherpad, I'll link that here since I noted it on there... 19:15:15 <Zara> #link https://etherpad.openstack.org/p/zuulv3-issues 19:16:03 <Zara> I'd've preferred a story, though I know some folk have been having issues with login that I don't think anyone has got to the bottom of yet 19:16:14 <Zara> I couldn't log in to storyboard-dev last night :/ 19:16:23 <Zara> regular storyboard.o.o worked, though 19:16:32 <Zara> as did my personal instance 19:17:21 <Zara> server logs from an affected instance could be helpful, maybe a db dump... not sure what else could be useful for debugging that 19:17:37 <SotK> yeah, it has been broken for a while 19:17:56 <Zara> it worked for me until yesterday but that might be to do with a token needing refreshing at that point, idk 19:18:07 <SotK> I'm not sure what the cause is, I suspect something is misconfigured 19:18:49 <Zara> I'm concerned as some people have reported it on s.o.o as well as dev, and also even if it were just dev, that's an issue for training etc 19:19:41 <Zara> and as there are some email issues too, seems like a good time to investigate the deployment more generally 19:19:50 <SotK> I think the issue some folk have had on s.o.o is different, in all but one case of that it has been a transient issue whereas dev has been giving me a (different) reproducible error 19:20:03 <Zara> oh, okay 19:20:31 <Zara> that's frustrating in one way but maybe better news for dev at least 19:20:48 <SotK> but yes, it would be good to try to improve things across the board, I agree 19:20:55 <Zara> if we have a list of things that'd help with debugging, maybe we can send it infra's way 19:21:08 <Zara> since aiui that's the way to get a db dump or some server logs 19:21:34 * SotK will organise something 19:21:39 <Zara> thanks 19:22:00 <Zara> I was a bit wary of this ending up as a hazy 'investigate' task where nothing happens 19:22:18 <Zara> so trying to come up with concrete stuff we can do when we know nothing :) 19:24:25 <SotK> :) 19:24:32 <SotK> anything else in progress? 19:25:03 <Zara> there was the docs patch 19:25:23 <diablo_rojo> johnsom's patch? 19:25:27 <Zara> #link https://review.openstack.org/#/c/506812/ 19:25:29 <Zara> yeah 19:25:58 <Zara> tl;dr: currently links to gh because of limitations of rendered docs anchoring with our current tooling 19:26:17 <Zara> would prefer release time to have rendered docs somewhere more official so it can be anchored there 19:26:30 <diablo_rojo> Ah. Makes sense. 19:26:41 <diablo_rojo> Yeah I remember now. Debate about where to link to 19:27:11 <johnsom> Yeah, no deep links when pointing to the text on git.o.o 19:27:32 <Zara> yeah, there's some discussion in the comments there about options, I've held off merging until that's settled, though we should be aware of it when projects migrate so that we can give them that info in the meantime 19:28:02 <johnsom> It became more that I had time for to try to move the doc and I couldn't just link to it from the docs, it didn't render well. 19:28:36 <diablo_rojo> It happens, we are all super busy johnsom :) 19:28:47 <johnsom> BTW, any news on getting emails working? Grin 19:29:13 <Zara> none yet though I believe it's now our top priority 19:29:21 <Zara> we are inching forward 19:29:42 <johnsom> Ok. Ping me if you want me to see if it starts working 19:30:04 <Zara> thanks :) (also re: the docs patch, I think it's a useful patch and would like it in there before too many teams migrate, even if we have to link to a gh version) 19:30:18 <Zara> (still hoping we can avoid gh linking but most important thing is that the teams have that info imo) 19:30:50 <diablo_rojo> Agreed. I care less about how it looks so long as the info is there. 19:31:09 <diablo_rojo> Its not like most people havent seen a gh page anyway ;) 19:31:57 <Zara> heh, considering saying something like 'if it gets to a point where we have x number of teams waiting for it, we merge, tidy later'. 19:32:50 <Zara> I think that's everything that's in-progress 19:34:13 <SotK> #topic Discussion 19:34:18 <Zara> can we put together a plan for emails debugging/fixing? 19:34:56 <Zara> I'm not sure what info to assemble; I estimate that I last got emails around july. 19:35:46 <Zara> yes, july 21st 19:36:49 <Zara> so a starting point might be to go back to around then in db and gerrit and see what changed 19:37:14 <Zara> and another thing would be to get a list of people we know are/aren't affected and look for differences 19:37:24 <SotK> I will ask you some questions after the meeting 19:37:36 <Zara> that's my idea of where to start with it, anyway, but it's a pretty hazy plan 19:37:41 <SotK> seems sensible 19:38:11 <Zara> okay, we should also write stuff up in a story so we can point people at it etc 19:38:14 <SotK> I'd like to get logs from the email workers, and see if any of them have had some kind of trouble 19:38:15 <Zara> I think there was one 19:38:47 * Zara finds https://storyboard.openstack.org/#!/story/2001229 19:38:53 <Zara> not sure if that was the only one but related anyway 19:40:33 <SotK> that one was discovered at the same time but turns out to be unrelated afaict 19:41:13 * Zara makes a story 19:41:16 <Zara> #link https://storyboard.openstack.org/#!/story/2001263 19:41:27 <SotK> thanks Zara 19:42:53 <Zara> added some scrawly tasks 19:43:19 <Zara> feel free to make them less scrawly 19:43:27 <Zara> just writing stuff up from here so I don't lose it 19:45:12 <Zara> that's all I had, I figure that's the first step to get moving toward a fix 19:45:24 <SotK> yep, it is a sensible step 19:45:43 <Zara> now I've written it down I can completely forget it!~ =D 19:47:07 <SotK> heh :D 19:47:09 <SotK> anything else? 19:47:15 <Zara> _o_ 19:48:25 <SotK> then thanks everyone for coming! 19:48:27 <SotK> #endmeeting