Comment 5 for bug 1662626

Matt Riedemann (mriedem) wrote :

Is this really an ocata release candidate potential bug? It sounds pretty latent and something we can backport to stable/ocata after 15.0.0 is released. Or was this the result of a regression in Ocata itself?