I don't think so as far I remember I started seeing this one or two weeks ago.
So basically what happened:
A job request a node from the pool, start running and immediately receive a no space left issue, job fails and the node return to the available pool like here.
As the node return to the available pool, this issue is hit as long as the job is assigned the same node.
As a workaround, I have to manually flag the need as unavailable.
As you can see on the screenshot, it seems like jenkins doesn't detect that the wrong node (third on the picture), doesn't detect disk space.