Invalid argument in threadgroup.Thread.wait
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Expired
|
Medium
|
Unassigned | ||
keystonemiddleware |
Invalid
|
Undecided
|
Unassigned | ||
oslo.concurrency |
Expired
|
Undecided
|
Unassigned |
Bug Description
When using Trove an Invalid argument error was encountered via Oslo's threadgroup.
http://
To reproduce in Trove: make an /instances call for a valid tenant id (in the URI) that does not match the valid X-Auth-Token. Example:
http://
Header: X-Auth-Token: mikes-token
There are probably more straightforward ways to reproduce this, but this is how I encountered it.
--
For trove specifically, my api-paste.ini config:
[filter:authtoken]
paste.filter_
auth_host = 10.0.1.40
auth_port = 35357
auth_protocol = http
admin_tenant_name = service
admin_user = trove
From trove.conf:
[keystone_
admin_user = trove
admin_tenant_name = service
auth_uri = http://
identity_uri = http://
auth_protocol = http
auth_port = 35357
auth_host = 10.0.140
description: | updated |
description: | updated |
Changed in trove: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → ongoing |
description: | updated |
description: | updated |
Based on conversations with Jonathan, I'm marking this as incomplete in Keystonemiddleware. We can't cleanly duplicate it, but if it resurfaces / etc we'll revisit/reopen.