stratis-storage/stratis-cli

NameHasNoOwner conclusion in _error_reporting.py is probably too certain

Closed this issue · 1 comments

It can be raised when calling get_object on a non-existent object path. Usually we call get_object on the top object, and if that fails then it is likely that the explanation is correct. But it could happen for any object path, and in those cases, then the explanation is much too certain. We should probably re-raise a StratisCli exception in get_object and include information about what object path we were trying to get, and then infer more about the situation from that.

I think I was wrong about this and misinterpreted an error I was seeing: stratis-storage/stratisd#2055 (comment), closing.