yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #23624
[Bug 1379358] Re: Changes in openstack_dashboard/conf/*policy.json won't take effect for Panel visibility until User re-logins
@Thiago, sure, the fix should be pretty simple, will upload it in a
while.
** Changed in: horizon
Status: Opinion => Confirmed
--
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/1379358
Title:
Changes in openstack_dashboard/conf/*policy.json won't take effect for
Panel visibility until User re-logins
Status in OpenStack Dashboard (Horizon):
Confirmed
Bug description:
The Panel class is a subclass of HorizonComponent class, which should
check `self.policy_rules` while determining whether the entity is
visible or not. Unfortunately the actual values `self.policy_rules`
relies upon are being loaded during first request to Horizon, also the
final result of checking whether Panel is visible or not will be
cached in user session.
Speaking of concrete example, for Identity -> Users panel
https://github.com/openstack/horizon/blob/2014.2.rc1/openstack_dashboard/dashboards/identity/users/panel.py#L29
you can check it yourself by changing both rules in
https://github.com/openstack/horizon/blob/2014.2.rc1/openstack_dashboard/conf/keystone_policy.json#L43
to "!" and see that the panel is still visible - until you _both_
reload Horizon and re-login to clear session. After that it will be
hidden.
While reloading Horizon is fine - because changing kind of server
settings is involved, the need to sign-out and the sign-in for the
visibility changes to take effect is not.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1379358/+subscriptions
References