yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #59207
[Bug 1645632] [NEW] policy.v3cloudsample.json still broken in Newton
Public bug reported:
This policy file works using the CLI clients; however, it does NOT work
with Horizon, yet again. This is the same problem I observed with
Mitaka, that forced me to revert to the liberty policy file. I've had
to do that again.
Error message for user who just logged in linked below. This is a problem that we need to fix, and I can recreate the issue at will.
https://gist.githubusercontent.com/jjahns/970daf472abea086403269920280d53c/raw/64480893b4cb1f65f63d48bbf05391597c5db74d/gistfile1.txt
My workaround has been to take the liberty V3 policy json file and copy
it into openstack_dashboard/conf/keystone_policy.json. That appears to
be fully functional, but we need to fix this behavior as having a policy
from 2 versions ago does not make any sense.
** Affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1645632
Title:
policy.v3cloudsample.json still broken in Newton
Status in OpenStack Identity (keystone):
New
Bug description:
This policy file works using the CLI clients; however, it does NOT
work with Horizon, yet again. This is the same problem I observed
with Mitaka, that forced me to revert to the liberty policy file.
I've had to do that again.
Error message for user who just logged in linked below. This is a problem that we need to fix, and I can recreate the issue at will.
https://gist.githubusercontent.com/jjahns/970daf472abea086403269920280d53c/raw/64480893b4cb1f65f63d48bbf05391597c5db74d/gistfile1.txt
My workaround has been to take the liberty V3 policy json file and
copy it into openstack_dashboard/conf/keystone_policy.json. That
appears to be fully functional, but we need to fix this behavior as
having a policy from 2 versions ago does not make any sense.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1645632/+subscriptions