oslo.middleware.sizelimit configuration conflict
Bug #1368490 reported by
Richard Jones
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Invalid
|
Undecided
|
Unassigned | ||
| oslo.middleware |
Fix Released
|
High
|
Davanum Srinivas (DIMS) | ||
Bug Description
If the oslo.middleware package is installed in a keystone installation and any of the middleware in it included in keystone's pipeline then the application will error with a configuration conflict due to oslo.middleware
This ultimately blocks keystone from using oslo.middleware. Whether it's a bug in oslo or in keystone is debatable, but the bug had to be filed somewhere :)
Revision history for this message
| Doug Hellmann (doug-hellmann) wrote | #1 |
| Changed in oslo.middleware: | |
| milestone: | none → next-kilo |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Steve Martinelli (stevemar) wrote | #2 |
| Changed in keystone: | |
| status: | New → Invalid |
Revision history for this message
| Doug Hellmann (doug-hellmann) wrote | #3 |
| Changed in oslo.middleware: | |
| assignee: | nobody → Davanum Srinivas (DIMS) (dims-v) |
| status: | Triaged → Fix Committed |
| Changed in oslo.middleware: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
We should namespace all of the oslo options so they don't end up in the default group used by applications. We should also ensure that all of our options are only being registered at runtime, so conflicts would only arise if we did have 2 sections of code trying to use the same option name in different ways.