EmptyCatalog raised when the catalog is not empty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
keystoneauth |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I'm creating a session inside of a Mistral action with something like
Session(
(where Token is keystoneauth.
2018-07-25 14:58:43.128 6277 ERROR mistral.
2018-07-25 14:58:43.128 6277 ERROR mistral.
2018-07-25 14:58:43.128 6277 ERROR mistral.
2018-07-25 14:58:43.128 6277 ERROR mistral.
2018-07-25 14:58:43.128 6277 ERROR mistral.
2018-07-25 14:58:43.128 6277 ERROR mistral.
2018-07-25 14:58:43.128 6277 ERROR mistral.
2018-07-25 14:58:43.128 6277 ERROR mistral.
2018-07-25 14:58:43.128 6277 ERROR mistral.
2018-07-25 14:58:43.128 6277 ERROR mistral.
2018-07-25 14:58:43.128 6277 ERROR mistral.
2018-07-25 14:58:43.128 6277 ERROR mistral.
2018-07-25 14:58:43.128 6277 ERROR mistral.
Whatever causes it, the exception is not true: I certainly have a populated catalog. If the problem is on the caller side, a clearer exception is needed.
What I figured out so far is that Token creates unscoped auth_refs even if the initial token was project scoped. And the service catalog is indeed not present. However, it's still confusing for the caller, and I still have no clue what to fix.