Service catalog randomly returned endpoint if there were multiple choice.
Bug #1771240 reported by
Yang Youseok
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| keystoneauth |
Triaged
|
Low
|
Unassigned | ||
Bug Description
in keystoneauth1/
endpoint_data_for() function just returned first candidate of entry points by endpoint_
Since there is no guarantee for endpoint order, I found that if client API did not specify any scope like region, an endpoint returned is changed randomly.
imho, library code should provide precisely defined behavior, so that client can expect and maybe this case could raise mulitiple choice exception.
Thanks.
| summary: |
- Service catalog randomly returned endpoints if there were multiple + Service catalog randomly returned endpoint if there were multiple choice. |
| description: | updated |
Revision history for this message
| Morgan Fainberg (mdrnstm) wrote | #1 |
| Changed in keystoneauth: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
This is reasonable, but will likely need to be opt-in to conform to the keystoneauth strict contract for behavior.