#opendaylight-meeting: md_sal_interest_call
Meeting started by tbachman at 16:03:47 UTC
(full logs).
Meeting summary
- bug scrub (tbachman, 16:03:59)
- ttkacik1 says there are no incoming “easy” bugs
since last weeks, so maybe we should look into unassigned bugs and
prioritize them (tbachman,
16:07:19)
- moizer asks if we already have takers for all
of the bugs from last week’s “easy” list (tbachman,
16:08:15)
- ttkacik1 says yes (tbachman,
16:08:18)
- tbachman asks if the bugs list is for all
projects, or across all projects (tbachman,
16:09:56)
- ttkacik1 says the cross-project bugs are
tracked in the Wednesday morning IRC meeting (tbachman,
16:10:23)
- ttkacik1 says bug 2155 is a medium level bug,
and is in RESTCONF, and has to do with how deep the structure is
desired by the user. (tbachman,
16:10:57)
- ttkacik1 says he can help anyone who can take
the bug with details in how to implement this in the RESTCONF
(tbachman,
16:11:17)
- catohornet asks if moizer’s volunteer could
take this (tbachman,
16:11:39)
- moizer says he’d have to check with
abhijitkumbare, as it’s technically his volunteer (tbachman,
16:11:53)
- debalina says she can take 2155 (tbachman,
16:12:12)
- ACTION: debalina to
take on bug 2155 (tbachman,
16:12:25)
- maros says that bug 1135 is quite old — we
should check with edwarnicke to get a better understanding of what
was meant but the bug report (tbachman,
16:13:07)
- ACTION: maros to
reach out to edwarnicke to ask him what the issue is — provide more
details (tbachman,
16:13:40)
- icbts says he can also look into that bug —
might be something like a log4j setting (tbachman,
16:14:08)
- edwarnicke says that bug 1135 is *simply*
complaining about the crypticness of the message, and is not
complaining that there is a bug in functionality (tbachman,
16:14:57)
- maros says bug 1946 is a complaint about the
wrong response code from RESTCONF. It’s an issue with the exception
hierarchy — already another bug open on this issue, and this is just
a symptom (tbachman,
16:16:18)
- maros says the main issue is tracked in bug
1110 (tbachman,
16:16:41)
- catohornet says it looks like bug 2320 is
difficult to reproduce (tbachman,
16:18:49)
- moizer says he doesn’t know if this is
happening any more, and even if it is, he thinks it’s likely to be
more of an issue with the app itself (tbachman,
16:19:27)
- catohornet asks if we can verify, resolve,
close, etc.? (tbachman,
16:19:35)
- ttkacik1 says 2320 is an incorrect use of the
data store. Should be closed and marked as invalid (tbachman,
16:20:15)
- ACTION: catohornet to
mark 2320 as resolved/invalid (tbachman,
16:23:48)
- ttkacik1 sasy bug 2375 isn’t a bug — it’s a
performance improvement in yangtools. If there are any takers, he
can walk them through the bug (tbachman,
16:25:06)
- ACTION: debalina to
take 2375 (tbachman,
16:26:43)
- moizer says bug 2523 might be difficult to
reproduce (tbachman,
16:27:55)
- moizer says lets keep it around, but take it
out of bugs to review (tbachman,
16:28:08)
- maros says that for bug 2679, we need to update
the library and remove the workaround — only issue with the
workaround is a performance impact (tbachman,
16:30:25)
- maros says if no one picks it up, they’ll try
to fix this in time for the Lithium release; only implementations
that expose EXI are affected by this (tbachman,
16:32:12)
- catohornet asks ttkacik1 what the status is
with Bug 3051 (tbachman,
16:34:45)
- ttkacik1 says the bug fix is merged in master,
but not stable/lithium, b/c the classes that use this are still
putting invalid input to it (tbachman,
16:35:04)
- ttkacik1 says the bugfix for 3051 in yangtools
uncovered bugs in other projects (tbachman,
16:35:53)
- ttkacik1 says there’s a patch for 3051 in at
least one branch that’s not yet merged; not merged b/c once it
merges, the verify merge jobs will not work for the openflowplugin
until they fix their bug related to this (tbachman,
16:36:58)
- ttkacik1 says they’re waiting on the downstream
projects to fix their bugs before they put the patch in, so that
they don’t break the downstream projects (tbachman,
16:37:26)
- ghall says kot-begemot might be able to help
with this (tbachman,
16:37:53)
- ghall asks what other projects are dependent on
this (tbachman,
16:40:53)
- ttkacik1 says it’s OVSDB, openflowplugin, and
groupbasedpolicy (tbachman,
16:41:02)
- tbachman asks if we can clone yangtolls and
cherry-pick the patch to stable/lithium and test (tbachman,
16:42:14)
- ttkacik says yes — you should get indications
about the invalid values (tbachman,
16:42:27)
- maros says that they haven’t yet analyzed bug
3134 — can’t tell if it’s an easy fix or something more
complicated (tbachman,
16:42:53)
- catohornet asks what the next step is for 3134
— try to reproduce? (tbachman,
16:45:01)
- maros says yes — someone should try to
reproduce the issue and debug (tbachman,
16:45:13)
- maros says you just run the feature test for
the project — the part where the config pusher is involved is
identical for all of the single-feature-tests (tbachman,
16:45:57)
- bug 3138 is the same as 3134 with just a
different result (tbachman,
16:47:13)
- abhijitk_ asks about bug 3051 — about the
downstream projects needing to be fixed before they can merge the
fix for 3051. abhijitk_ asks what the fixes are for the downstream
projects (tbachman,
16:48:12)
- ttkacik1 says 3051 is blocking the
openflowplugin from version-bumping to beryllium yangtools, due to
incorrect use of IpPrefixes (tbachman,
16:48:50)
- abhijitk_ asks if kot-begemot’s changes are the
best way to get things unblocked (tbachman,
16:49:21)
- kot-begemot says the changes are to pass
prefixes instead of IP address in a few places, but in a few places
in the openflowplugin, you can’t fix the test cases b/c the
openflowplugin’s match conversion code to openflow semantics makes
the assumption that an IP address by itself is an allowed
match (tbachman,
16:50:38)
- kot-begemot says this used to work, but you
need to change the conversion code (tbachman,
16:50:52)
- ttkacik1 says he’s seen patches for the
openflowplugin, but just needs to review them (tbachman,
16:51:31)
- kot-begemot says that code has grown
“organically”, so there’s fixes needed and a minimal amount of
cleanup in order to make it comprehensible (tbachman,
16:52:11)
- alagalah asks ttkacik1 if he’s saying that you
can't merge it to YangTools StableLi, because once you do, projects
like GBP who haven't cut will break (thanks!) but also that you are
waiting on OFP, who we are also waiting on ... it seems like a
circular dependency (tbachman,
16:53:12)
- ttkacik1 says yes (tbachman,
16:53:17)
- ttkacik1 says if we merged the bug fix to
yangtools now would break the downstream projects (tbachman,
16:53:46)
- https://git.opendaylight.org/gerrit/#/c/20704
The gerrit from kot-begemot that provides utility functions for
projects to fix this (tbachman,
16:55:38)
- ACTION: tbachman to
make the fixes for this in groupbasedpolicy (tbachman,
16:57:25)
Meeting ended at 16:59:12 UTC
(full logs).
Action items
- debalina to take on bug 2155
- maros to reach out to edwarnicke to ask him what the issue is — provide more details
- catohornet to mark 2320 as resolved/invalid
- debalina to take 2375
- tbachman to make the fixes for this in groupbasedpolicy
Action items, by person
- catohornet
- catohornet to mark 2320 as resolved/invalid
- edwarnicke
- maros to reach out to edwarnicke to ask him what the issue is — provide more details
- tbachman
- tbachman to make the fixes for this in groupbasedpolicy
- UNASSIGNED
- debalina to take on bug 2155
- debalina to take 2375
People present (lines said)
- tbachman (65)
- alagalah (6)
- odl_meetbot (4)
- edwarnicke (2)
- ttkacik1 (1)
- catohornet (0)
Generated by MeetBot 0.1.4.