I’m sorry that I’m not right on the case.
I wonder about this issue. The specifics of the problem you’re running into seems, to me, to indicate that there is no Storage groups with a master node within the group. Normally it should default to return the relative node that IS in that particular group, but if there is no node associated, this could occur, I suppose. I don’t know all the specifics. I’m working, hopefully, to figure out a solution, but I feel I may need access to a problematic system so I can work on it live. Sometimes, and there are multiples who can verify this as needed, I simply can’t replicate so seeing the problem on a known “bad” target is really the best option.