On Mon, Oct 24, 2016 at 11:57 PM, Josh Durgin <jdurgin@xxxxxxxxxx> wrote: > On 10/20/2016 06:52 AM, Sage Weil wrote: >> >> On Thu, 20 Oct 2016, Loic Dachary wrote: >>> >>> H Sage, >>> >>> It looks like http://tracker.ceph.com/issues/15454 surfaced in jewel >>> (failed twice in a row at http://tracker.ceph.com/issues/17487#note-19). It >>> did not occur before, therefore I suspect it's a side effect of some of the >>> commits in the jewel backports integration branch ( >>> http://tracker.ceph.com/issues/17487#note-16 ), but I don't see which commit >>> in that branch could have caused that kind of misbehavior. >>> >>> Since you marked http://tracker.ceph.com/issues/15454 as Resolved with no >>> commits attached, I suppose it means it went away for some reason. Could you >>> please confirm ? >> >> >> Hmm, unfortunately I don't remember working on this one. My guess is it >> came up during a bug scrub discussion and that's when it got closed. >> Hopefully Kefu or Josh remember? > > > I don't think I've seen that particular bug before, so hopefully Kefu > remembers it. neither do i remember this, i investigated it a little bit. but had no clues then. no idea why we closed it. > > > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Regards Kefu Chai -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
