07-09-2019 06:26 AM
I still encountered this bug with Prime Infrastructure 3.6.0 Update 01!
In the bug report it is marked as "fixed", but the count for "known fixed releases" is 0!
So is there anywhere a fix available?