As @Hooverdan indicated, we have seen this before. But I’m pretty sure that since it came up again more recently here:
We have identified the main cause and released the fix in 5.0.13-0 (RC8), with @Stevek confirming the fix for their install at least. This pertained to imported pools only.