Catalog can't handle multiple service definitions
Bug #1425766 reported by
Jamie Lennox
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-keystoneclient |
Fix Released
|
Medium
|
Jamie Lennox | ||
Bug Description
The keystoneclient can only handle one entry in the service_catalog for each service_type. While IMO this is a reasonable assumption the keystone service does not enforce this rule, and there are deployments that are already doing this.
This was never much of a concern for keystone, however now that keystone sessions are providing the foundation for the various clients this has become a problem as novaclient and other used to support it.
This bug has been reported in the past and marked as either Opinion or Invalid. I couldn't find them to reopen.
| Changed in python-keystoneclient: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| importance: | Medium → High |
| importance: | High → Medium |
Revision history for this message
| Morgan Fainberg (mdrnstm) wrote | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to python-keystoneclient (master) | #2 |
| Changed in python-keystoneclient: | |
| assignee: | nobody → Morgan Fainberg (mdrnstm) |
| status: | Triaged → In Progress |
| assignee: | Morgan Fainberg (mdrnstm) → Jamie Lennox (jamielennox) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on python-keystoneclient (master) | #4 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to python-keystoneclient (master) | #5 |
| Changed in python-keystoneclient: | |
| status: | In Progress → Fix Committed |
| Changed in python-keystoneclient: | |
| milestone: | none → 1.2.0 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Likely the easiest solution here is to simply combine the endpoints if two services claim to be the exact same thing (e.g. "compute" should == "compute").