Docs might be wrong for configuring keystone access params
Bug #1931875 reported by
Dan Smith
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| oslo.limit |
In Progress
|
Undecided
|
Jneeee | ||
Bug Description
This is a placeholder bug to discuss with Lance when he returns. I believe that while I was trying to get the initial glance unified quota stuff working, we identified some incorrect or missing bits of the setup and configuration noted here:
https:/
which ended up different in the actually-working devstack support:
https:/
Revision history for this message
| Jneeee (jnl2) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to oslo.limit (master) | #2 |
| Changed in oslo.limit: | |
| status: | New → In Progress |
| Changed in oslo.limit: | |
| assignee: | nobody → Jneeee (jnl2) |
To post a comment you must log in.
I found this bug recently too: the endpoint_id must be supplied otherwise enforce quota will fail.
I think we can get endpoint_id from keystone if the service name and service type are provided. I will push a commit relate to this.