Comment 11 for bug 1815154

Without digging too deep, it's not likely to be a facade version issue - status uses existing storage facade api calls that have been part of juju since 1.x and are already used with the juju list-storage command - status simply makes the same api calls as that other CLI and displays the same info.

It's more likely simply a permission check issue not encountered before - no one ever ran juju list-storage against a model they didn't own.