yahoo-eng-team team mailing list archive

[Doug Hellmann <doug@xxxxxxxxxxxxxxxx>]

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.


** Also affects: keystone
   Importance: Undecided
       Status: New

** Changed in: oslo.middleware
    Milestone: None => next-kilo

** Changed in: oslo.middleware
       Status: New => Triaged

** Changed in: oslo.middleware
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1368490

Title:
  oslo.middleware.sizelimit configuration conflict

Status in OpenStack Identity (Keystone):
  New
Status in Oslo WSGI middleware library:
  Triaged

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.sizelimit adding the configuration option
  max_request_body_size which is already added by the keystone
  middleware RequestBodySizeLimiter.

  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 :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1368490/+subscriptions