Can you attempt to reproduce this against the latest upstream git? I believe a fix for this has been committed and we probably need to backport it to stable.
Can you attempt to reproduce this against the latest upstream git? I believe a fix for this has been committed and we probably need to backport it to stable.