23 Feb
2017
23 Feb
'17
8:58 a.m.
On 23 February 2017 at 16:51, Yaniv Kaul <ykaul@redhat.com> wrote:
It's very confusing that this error is sometimes harmless and sometimes isn't - how did you identify it as problematic? Y.
If you're asking me, it was because this failed on the same issue for 12 OST runs straight. -- Barak Korren bkorren@redhat.com RHCE, RHCi, RHV-DevOps Team https://ifireball.wordpress.com/