14:00:19 #startmeeting nova 14:00:23 Meeting started Thu Oct 31 14:00:19 2019 UTC and is due to finish in 60 minutes. The chair is efried. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:25 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:27 The meeting name has been set to 'nova' 14:00:30 o/ 14:00:33 o/ 14:01:40 #link agenda https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting 14:03:33 #topic Last meeting 14:03:34 #link Minutes from last meeting: http://eavesdrop.openstack.org/meetings/nova/2019/nova.2019-10-24-21.00.html 14:03:55 was a short one, just me & mriedem, with a guest appearance by smcginnis. News from that encounter forthcoming. 14:04:02 #topic Release News 14:04:02 #link Nova Ussuri schedule https://wiki.openstack.org/wiki/Nova/Ussuri_Release_Schedule 14:04:02 #link Queens is em https://review.opendev.org/#/c/692142/ 14:04:20 mriedem: anything to note on queens em? 14:04:49 it's done 14:05:06 there are open +2ed changes so we're still merging code, 14:05:08 but it won't be released 14:05:18 thanks 14:05:18 #topic Summit/PTG Planning 14:05:18 #link PTG etherpad https://etherpad.openstack.org/p/nova-shanghai-ptg 14:05:18 #link Do PTG stuff virtually if appropriate http://lists.openstack.org/pipermail/openstack-discuss/2019-October/thread.html#10363 14:05:18 #link If you need cross-project sessions, put 'em on there http://lists.openstack.org/pipermail/openstack-discuss/2019-October/thread.html#10422 14:05:36 neither of you will be in Shanghai? 14:05:43 nope 14:06:23 i expect the barrage of product manager requirements getting translated to the cores that are there will be fun for them 14:06:39 "product manager"? 14:06:51 i suspect there will be a lot of non-developer people in the ptg rooms 14:07:31 e.g. "we have a customer that wants nova to make ice cream on demand and in a cron, should we write a spec?" 14:07:35 that might not be a terrible thing to have actual operators voicing requirements rather than the usual dev echo chamber of what we think the world needs. 14:07:43 i'm not talking about operators 14:07:45 hah 14:08:06 point taken. 14:08:13 Making ice cream would be cool 14:08:19 moving on. 14:08:23 #topic Stable branch status 14:08:23 #link stable/train: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/train 14:08:23 #link stable/stein: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/stein 14:08:23 #link stable/rocky: https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/rocky 14:08:23 #link stable/queens: (will be removed) https://review.openstack.org/#/q/status:open+(project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/nova)+branch:stable/queens 14:08:24 i should tell stephen to friend up with fred li and he can yell at people that are off track 14:09:10 mriedem: okay to stop tracking queens there --^ or should we keep watching until some number of the pending patches merge? 14:09:18 stop tracking it here 14:09:27 ack 14:09:28 #topic Bugs (stuck/critical) 14:09:28 No Critical bugs 14:09:28 #link 87 new untriaged bugs (+0 since the last meeting): https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 14:09:28 #link 8 untagged untriaged bugs (-1 since the last meeting): https://bugs.launchpad.net/nova/+bugs?field.tag=-*&field.status%3Alist=NEW 14:10:01 #topic Gate status 14:10:01 #link check queue gate status http://status.openstack.org/elastic-recheck/index.html 14:10:01 #link 3rd party CI status http://ciwatch.mmedvede.net/project?project=nova 14:10:21 ahem, ^ seems dead again 14:10:32 the gate is f'ed 14:10:50 i've been rechecking the same changes for probably half a week 14:10:59 yeah, really bad 14:11:01 and it's not even feature freeze! 14:11:19 if you want some dumps, 14:11:24 mriedem, that tempst c-bak change is cursed 14:11:27 http://status.openstack.org/elastic-recheck/#1763070 is spiked again for some unknown reason 14:11:37 http://status.openstack.org/elastic-recheck/#1844929 is a huge fail rate with no end in sight 14:11:40 s/end/fix/ 14:11:55 and there are a whole bunch of random cirros guest setup failures that cause ssh to fail 14:11:59 like http://status.openstack.org/elastic-recheck/#1848078 14:12:02 http://status.openstack.org/elastic-recheck/#1808010 14:12:10 http://status.openstack.org/elastic-recheck/#1737039 14:12:15 http://status.openstack.org/elastic-recheck/#1840355 14:12:32 http://status.openstack.org/elastic-recheck/#1849857 14:12:41 the cirros guests are basically garbage right now 14:12:45 i don't know hy 14:12:46 *why 14:13:15 probably time for me or clarkb to write up a state of the gate email to the ML, i can do that after the meeting to raise the issue 14:13:23 thanks 14:14:00 i guess we should also hold off on recheck things that are not related to fixign the gate for a bit 14:14:09 g8 st8 14:14:13 if we do nothing will ever merge 14:14:17 no one is working on fixing gate bugs 14:14:45 disabling ssh in tempest api tests would get things flowing but that's not a good answer 14:14:59 yeah; I haven't seen a huge spike in rechecks lately for stuff I've been watching. More than usual, maybe a bit, but not more fails than successes like we had during ff. 14:15:31 feels like more fails than successes to me 14:15:41 maybe my patches are cursed 14:15:51 but it feels like it's almost at standstill 14:16:00 same 14:16:09 are most of the failure ssh/network related 14:16:15 no, 14:16:21 there are a lot that are kinda infra related 14:16:37 well, the cells db one is...idk 14:16:38 like the grenade database setup one, devstack timeouts waiting for something to happen 14:16:49 yum client mirrors is at the top 14:17:02 there are some known infra ones that get auto-rechecked by zuul i think 14:17:03 7 nova patches merged overnight. I think I had rechecked maybe three of them? 14:17:06 clarkb would know details on that 14:17:14 pip fail 14:17:28 for the stuff i'm rechecking, it's not infra failures 14:17:36 it's grenade and guest/ssh fails 14:17:57 well, I'm lumping the grenade db setup thing in as infra 14:18:15 i.e. not a tempest test that is failing 14:18:26 anyway 14:18:28 well, it is triggered by a tempest smoke run after upgrade 14:18:31 n-sch times out 14:18:45 but yeah it's not really a code bug 14:18:49 something f'ed up in mysql 14:18:52 right, it seems to be setup 14:18:56 that's my point 14:19:04 it also just randomly showed up and i don't know how to account for it 14:19:05 or debug it 14:19:09 yeah 14:19:12 we likely need zzzeek 14:19:32 or leakypipes! 14:20:43 efried: moving on? 14:20:52 Yah. Aforementioned action hopefully moves the ball. lmk if there's anything I can do to help. 14:21:19 #topic Reminders 14:21:20 any? 14:21:56 #topic Sub/related team Highlights 14:21:56 Placement (cdent/tetsuro) 14:22:33 things have been pretty quiet here. If you have something to talk about, the 14:22:33 #link placement ptg etherpad https://etherpad.openstack.org/p/placement-shanghai-ptg 14:22:33 would be a good place to put it. 14:22:45 API (gmann) 14:23:47 I think other than policy defaults stuff, nothing much here? 14:23:55 #topic Stuck Reviews 14:23:55 any? 14:24:21 #topic Review status page 14:24:21 #link http://status.openstack.org/reviews/#nova 14:24:21 Count: 464 (+5); Top score: 2182 (+52) 14:24:30 #topic Open discussion 14:24:37 Bueller? 14:24:50 nada 14:24:55 i abandoned a bunch of old reviews yesterday 14:25:08 doesn't put a dent in the open review 14:25:23 i wanted to hilight one bluepirnt that was just filed https://blueprints.launchpad.net/nova/+spec/config-tsc-freq 14:25:58 basicaly i just wanted to know if people think this needs a spec of not 14:26:35 what's the scope of the code change? Sounds small? 14:26:48 add a new flavor extraspec 14:26:55 and a minor libvirt dirver update 14:26:58 thats about it 14:27:27 eandersson might be interested in that 14:27:28 I think if you spell out the extra spec in the bp it should be able to go specless. 14:27:28 similar in scope the the pmu change i did last cycle 14:27:53 ya i can work to flesh it out in the blueprint 14:28:01 i think it's likely ok specless 14:28:20 i think we already have a spec for hpet timer stuff 14:28:23 just build on that 14:28:33 ok it was brought up by umbSublime on irc last week so i just want to help them along 14:28:45 hw_time_hpet image property, not extra spec 14:29:08 anything else? 14:29:24 Happy halloween everyone. 14:29:24 Well, everyone with pagan still in their heart. 14:29:24 o/ 14:29:24 #endmeeting