14:30:45 <anipbu> #startmeeting release
14:30:45 <odl_meetbot> Meeting started Wed Sep  7 14:30:45 2016 UTC.  The chair is anipbu. Information about MeetBot at http://ci.openstack.org/meetbot.html.
14:30:45 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:30:45 <odl_meetbot> The meeting name has been set to 'release'
14:30:52 <anipbu> #topic roll call
14:30:57 <gdavid_comp> #info gdavid_comp for unimgr
14:31:03 <anipbu> Welcome to the Boron Weekly Sync on IRC to discuss blocking bugs and red flags for the Boron Simultaneous Release
14:31:10 <anipbu> PTL please #info your projects so we can track and record your attendence
14:32:04 <yamahata> #info yamahata for neutron northbound
14:32:16 <michal-cmarada|2> #info Michal Cmarada for GBP
14:32:34 <lori> #info lori for lispflowmapping
14:32:54 <zxiiro> #info Thanh for releng
14:33:30 <skitt> #info skitt for odlparent
14:33:56 <anipbu> #info anipbu for usc, nemo
14:35:30 <anipbu> Any other folks please info your projects?
14:35:40 <anipbu> Anyone from HONEYCOMB / VBD?
14:35:44 <anipbu> Let's move on to agenda
14:35:48 <anipbu> #topic agenda
14:35:51 <anipbu> #info RC3
14:35:55 <anipbu> #info blocking bugs and red flags
14:35:59 <anipbu> Any other agenda topic folks would like to discuss in 30 minutes?
14:36:18 <tcere> #info tcere for netconf
14:37:03 <anipbu> Seems there is no additional topics from folks
14:37:07 <anipbu> Okay's get started
14:37:12 <anipbu> #topic RC3
14:37:17 <anipbu> #link https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_Plan#RC3   <-- Download for RC3
14:37:17 <michal-cmarada|2> #info I can speak for VBD regarding the blocking bug.
14:37:46 <anipbu> michal-cmarada|2>: good morning/night
14:37:56 <colindixon> #info colindixon for TSC, Docs, TTP, and mayhem
14:38:01 <anipbu> michal-cmarada|2>: can you elaborate on the severity of teh VBD bug?
14:38:27 <anipbu> colindixon: we are currently discussing blocking bug in vbd
14:38:35 * colindixon listens
14:38:56 <anipbu> michal-cmarada|2>: is this something we can delay to SR1 on October 6?
14:38:58 <michal-cmarada|2> anipbu: Without this bugfix we cannot create VXLAN tunnels, so FDS scenario will not work
14:39:19 <colindixon> is this a new regression in RC3?
14:39:29 <anipbu> michal-cmarada|2>: will waiting one month be okay?
14:39:31 <colindixon> was it present in RC0?
14:39:41 <michal-cmarada|2> FDS was targeted for Colorado Release on 16. of September
14:40:25 <michal-cmarada|2> so October 6 is too late for us.
14:40:27 <colindixon> understood, I'm just trying to understand why we're finding such a cirtical bug so late in the testing?
14:40:54 <colindixon> it sounds like any testing at all done in RC0 would have found it? or was it introduced somehow in RC3?
14:41:02 <michal-cmarada|2> The bug was found earlier, but was somehow forgotten and not merged.
14:41:32 <colindixon> OK
14:41:48 <anipbu> michal-cmarada|2>:   Any chance we can release note a workaround?  Is there no workaround?
14:42:01 <colindixon> is it only a problem for 3-node clustering?
14:42:15 <michal-cmarada|2> the bug was introduced on 2016-08-31 and was also tested by the date
14:42:24 <michal-cmarada|2> there is no workaround for this bug.
14:42:33 <anipbu> michal-cmarada|2>: or any hot fixes that can be published on the release notes?
14:43:45 <michal-cmarada|2> https://git.opendaylight.org/gerrit/#/c/44905/ this was the fix for this bug
14:44:16 <colindixon> michal-cmarada|2: what anipbu and I are trying to figure out is if there's a remediation for the problem other than rebuilding a new RC
14:44:30 <colindixon> so, that's why I was asking if it was only a problem for 3-node clustering
14:44:36 <colindixon> as the commit message for the bug syas
14:44:48 <michal-cmarada|2> curently there is none, that I am aware of.
14:44:53 <colindixon> and that's why anipbu is asking if there's a way to work around it that could e described in a release note
14:45:03 <colindixon> so it's also a problem when running without a cluster?
14:45:42 <michal-cmarada|2> yes, its also a problem when we are running without a cluster.
14:46:15 <colindixon> OK
14:46:42 <colindixon> #info michal-cmarada|2 says that this bug is a blocker for them in that it meand FDS can't work in the Colorado release of OPNFV on 9/16
14:46:42 <michal-cmarada|2> the VXLAN tunnels thet need to be configured on VPP nodes are overwriting so the communication between VPP nodes is not possible
14:47:38 <colindixon> #info it appears as though the bug was identified a week ago and fixed, and cherrry-picked to stable/boron, and even +2ed (by Wojciech), but not submitted and merged
14:48:11 <colindixon> #info there isn't a workaround, and (despite the commit message), applies both in clusters and not in clusters
14:48:48 <colindixon> #info it's a frusrating oversight and would have been *really* nice to catch with earlier testing of RC3, but it sounds like we'll need to respin
14:49:02 <colindixon> anipbu: are there other patches that we should wait for
14:49:15 <colindixon> should we respin at midnight UTC to give time for things to settle in the US?
14:49:27 <colindixon> or should we start the respin and know we can always do another one later in the day?
14:50:02 <anipbu> colindixon: there's a patch from netvirt that can be delayed for SR1, but if we're going to respin, let's add it in.
14:50:10 <colindixon> anipbu: sounds good
14:50:13 <zxiiro> There's currently a build in progress 7 hrs into the build. If we spin now we'll have to cancel it
14:50:28 <colindixon> michal-cmarada|2: for reference, this is why we like to have blocking bugs filed and tracked
14:50:40 <colindixon> so that there's extra eyes to catch mistakes like this
14:51:22 <michal-cmarada|2> colindixon: sure, I don`t know how we could missed this one it was crucial to us.
14:51:39 <anipbu> colindixon: zxiiro: we should respin after vbd fix is merged and current RC3 is complete.
14:51:52 <colindixon> make it so
14:52:02 <zxiiro> ok so about 2-3 more hours then
14:52:05 <colindixon> anipbu: other things we need to cover?
14:52:31 <colindixon> zxiiro: my guess is that we'll have more fixes to merge today, so waiting a few hours is fine
14:52:46 <colindixon> at least we can then test if we fixed the previous blockers while this is going on
14:55:18 <anipbu> colindixon: nope, vbd is the major topic to cover.
14:55:20 <anipbu> Exactly why I would like the current Boron build to continue.
14:55:21 <anipbu> #info plan of action for RC3: continue current RC3.1 build.  Projects will verify blocking bugs are fixed in that build.  The release team will respin RC3.2 once vbd/netvirt has merged their fixes.  FInal build become available by 9/8 Thursday.
14:55:50 <anipbu> Any other folks have questions or comments regarding RC3?
14:57:13 <anipbu> #topic blocking bugs and red flags
14:57:24 <anipbu> #info blocking bug in vbd, patch is waiting to be merged
14:57:36 <anipbu> #info blocking bug in netvirt
14:57:59 <anipbu> #link https://bugs.opendaylight.org/buglist.cgi?bug_severity=blocker&bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&bug_status=WAITING_FOR_REVIEW&f1=cf_target_milestone&f2=cf_target_milestone&j_top=OR&list_id=64394&o1=substring&o2=equals&query_format=advanced&resolution=---&v1=boron&v2=---
14:58:17 <anipbu> #info current list of blocking bugs in this spreadsheet: https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=294913046
14:58:32 <anipbu> Any last minute topics to raise from folks?
14:58:36 <anipbu> open mic
15:00:27 <anipbu> going once
15:00:29 <anipbu> going twice
15:00:35 <anipbu> Okay, thanks folks for joining.
15:00:40 <anipbu> #topic cookies
15:00:44 <michal-cmarada|2> Thank you all once again. bye
15:00:45 <colindixon> thanks!
15:00:46 <anipbu> #endmeeting