I think that the current behavior is appropriate; if for some reason we're calling getVolumes when the user doesn't have access, there should be some sort of stack trace on the server logs. The bug is more whether we should be checking something to help prevent that call from being made, not to change the getVolumes behavior.
** Changed in: horizon Status: New => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1414118 Title: Horizon shows stacktrace instead of 401: unauthorized Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: In Icehouse if a user is unauthorized to access volumes, horizon shows a popup upon login as well as when accesing volumes. In Juno, horizon shows no warning upon login, and as one access volumes it shows a stacktrace. One way to reproduce it is to edit on the cinder host the /etc/cinder /api-paste.ini file, and in the "filter:authtoken" section configure an auth_host that is not keystone. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1414118/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp