22:02:56 #startmeeting neutron_drivers 22:02:57 Meeting started Thu Aug 24 22:02:56 2017 UTC and is due to finish in 60 minutes. The chair is kevinbenton. Information about MeetBot at http://wiki.debian.org/MeetBot. 22:02:58 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 22:03:00 The meeting name has been set to 'neutron_drivers' 22:03:13 #topic announcements 22:03:27 RC2 just released today 22:03:51 armax: can you give us a snapshot of where we are with releases of everything else? 22:04:10 kevinbenton: everything else being? 22:04:12 is there anything we need to keep an eye on for the subprojects? IIRC we will need an RC3 for the DVR bug 22:04:18 in neutron itself 22:04:26 armax: everything else = rest of stadium 22:04:29 I thing we will 22:04:39 we have another week to cut other RCs if necessary 22:04:41 think^^^ 22:04:59 kevinbenton: did you keep track of the FFEs you granted? 22:05:43 technically speaking we probably only have one or two days left knowing the usual state of the gate during crunch time 22:05:53 the bug itself can always be backported later 22:06:38 we discussed the DVR bug earlier today during the L3 meeting 22:06:49 at this point we can only consider RC blocking issues to cut an RC3 22:06:56 but I can’t see any so far 22:07:33 ihrachys: welcome! 22:07:34 so you say better concentrate of back porting later? 22:07:48 mlavalle: yes 22:08:03 the security group logging didn't make the FFE 22:08:03 cool. I'll communicate that to the team 22:08:07 only fixes to catastrophic issues would be granted an RC exception by the release team at this point 22:08:26 armax: i think the DVR bug is catostrophic 22:08:33 doesn't it break all multi-node with HA? 22:08:36 mlavalle: ^^ 22:08:43 do we have a fix? 22:08:50 https://review.openstack.org/#/c/497009/ 22:08:52 we have a proposed fix 22:08:56 kevinbenton: it’s not catastrophic 22:08:59 it’s bad 22:09:21 but it’s not such that we release crap 22:09:46 are we sure that that fix doesn’t create N other bugs? 22:10:07 i don't understand, i don't think we can release if HA + DVR is broken 22:10:51 no point in arguing if the patch is ready to land, we have today and tomorrow to cut an RC3 for neutron 22:10:53 alone 22:11:00 but we should hurry 22:11:05 ok 22:11:20 ok 22:11:42 the last comment from swami doesn’t exude confidence 22:11:43 https://bugs.launchpad.net/neutron/+bug/1712412/comments/3 22:11:44 Launchpad bug 1712412 in neutron "DVR external port setup fails with KeyError: 'host'" [High,In progress] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan) 22:14:01 did I drop? 22:14:09 armax: no 22:14:17 armax: i was just looking at the patch and bug 22:14:39 i need to get some more details from Swami but this looks okay 22:14:42 who else besides you can vet this patch? Brian seems out 22:15:16 i'll catch brian in the morning 22:15:25 ihrachys: he's not on PTO anymore is it? 22:15:28 what about https://bugs.launchpad.net/neutron/+bug/1712728? 22:15:29 is he*? 22:15:30 Launchpad bug 1712728 in neutron "DVR: get_router_cidrs in dvr_edge_router not returning the centralized_floating_ip cidr" [High,In progress] - Assigned to Swaminathan Vasudevan (swaminathan-vasudevan) 22:15:33 I think he still is 22:15:36 sec 22:15:37 he is 22:15:53 this is another issue stemming from the same aftermath? 22:15:59 Monday he is back 22:16:09 armax: this is a bug with new functionality 22:16:17 armax: so i would be okay with back-porting later 22:16:33 centralized floating IPs with DVR is the new feature 22:17:23 both patches mention centralized floating IPs so it’s not clear 22:17:53 armax: the first patch we discussed is for a bug having side effects on old code paths 22:18:01 kevinbenton: I’d say we have 24 hours from now to put another release patch to release a neutron RC3 22:18:07 armax: this other bug appears to just be leaving central floating IPs behind 22:18:14 after that dims at al are gonna yell at us 22:18:25 armax: which is bad, but the only time for central floating IPs is if they are using the new feature 22:19:49 mlavalle: would you be comfortable reviewing the fix as well once we get some more details from swami? 22:19:58 kevinbenton: yes 22:20:21 mlavalle: ok, hopefully we can get that today, i see he just uploaded another patch so he might be around 22:21:02 ok 22:21:14 kevinbenton: OK, I’ll keep an eye on it, and I’ll file a WIP patch to the releases repo to alert the release team 22:23:24 ok, anything else to discuss? 22:23:43 i think next week we can resume normal drivers meetings to figure out what Queens is going to look like 22:23:52 not from me. let's focus on this 22:24:07 ok 22:24:26 amotoki is away anyway 22:24:30 ihrachys: any concerns from you/ 22:24:31 ? 22:24:33 no 22:24:47 * dims peeks 22:24:59 dims: looks like we will have an RC3 for one bug fix 22:25:10 y kevinbenton . no worries 22:25:10 dims: we only summoned you to ask for forgiveness 22:25:16 dims: patch is up but we need a little time to review it 22:25:27 dims: hopefully in gate tomorrow at latest 22:25:28 dims: is taht right that tomorrow is the last useful day to get an RC? 22:26:31 armax : i'd say take your time, but let's checkpoint tomorrow evening 22:26:46 dims: ack, thanks 22:26:47 OK 22:26:48 dims: that sounds better 22:26:54 dims: thanks 22:26:56 thanks 22:27:09 kevinbenton : will need input from smcginnis and dhellmann too, we can do that tomorrow 22:27:43 armax : kevinbenton : which review should i watch? 22:27:57 dims: https://review.openstack.org/#/c/497009/ 22:28:21 thanks kevinbenton 22:29:18 ok, thanks everyone 22:29:27 o/ 22:29:28 short meeting? 22:29:32 armax: yep 22:29:38 OK then 22:29:42 armax: unless you want to talk about anything else 22:29:52 i just dont' want to review any new feature related things this week 22:29:52 kevinbenton: you don’t want me to 22:30:04 armax: if it's release/pike focused, that's fine 22:30:10 nope 22:31:41 ok 22:31:48 #endmeeting