policy breaks TripleO
Bug #1812844 reported by
Juan Antonio Osorio Robles
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| novajoin |
Fix Released
|
Critical
|
Juan Antonio Osorio Robles | ||
Bug Description
The policy introduced recently [1] breaks TripleO deployments. This is because in TripleO we only rely on the project (the "service" project), and don't have a "service" role.
| Changed in novajoin: | |
| importance: | Undecided → Critical |
| status: | New → Triaged |
| Changed in novajoin: | |
| assignee: | nobody → Juan Antonio Osorio Robles (juan-osorio-robles) |
| Changed in novajoin: | |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to novajoin (master) | #1 |
| Changed in novajoin: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Zuul
Branch: master
commit 5633d348e3307a5
Author: Juan Antonio Osorio Robles <email address hidden>
Date: Tue Jan 22 13:51:34 2019 +0200
Change default policy to check service project and not role
In TripleO and devstack alike, service users are part of the "service"
project; while TripleO doesn't have a "service" role. So lets depend on
the project to enforce policy. This way this will still work out of the
box with TripleO.
Change-Id: I01cf7b38904bb0
Closes-Bug: #1812844