On 04/05/2021 09:49, Frank Schilder wrote:
We just observed this very issue on Pacific (16.2.10) , which I also
commented on the ticket.
I wonder if this case is so seldom, first having some issues causing
slow ops and then a total failure of an OSD ?
Would be nice to fix this though to not "block" the warning status with
something that's not actually a warning.