yahoo-eng-team team mailing list archive

[Thomas Goirand <thomas@xxxxxxxxxx>]

Public bug reported:

Depending on what's in the flavor directive of /etc/glance/glance-
registry.conf, glance-registry searches for a different section of
/etc/glance/glance-registry-paste.ini. For example, if I put flavor =
keystone+caching, then glance-registry searches for a section [pipeline
:glance-registry-keystone+caching] in /etc/glance/glance-registry-
paste.ini.

If this is a feature, then the default configuration file should be
updated to handle all values of the flavor directive.

If it's a bug (eg: regression) and that glance-registry is searching for
the wrong section, then this should be corrected.

In the mean while, I'm patching the default configuration file in my
Debian package to add the below lines to glance-registry-paste.ini:

[pipeline:glance-registry-keystone]
pipeline = osprofiler unauthenticated-context registryapp

[pipeline:glance-registry-caching]
pipeline = osprofiler unauthenticated-context registryapp

[pipeline:glance-registry-keystone+caching]
pipeline = osprofiler unauthenticated-context registryapp

[pipeline:glance-registry-cachemanagement]
pipeline = osprofiler unauthenticated-context registryapp

[pipeline:glance-registry-keystone+cachemanagement]
pipeline = osprofiler unauthenticated-context registryapp

Without this, glance-registry may refuse to start by default, which is
really annoying.

** Affects: glance
     Importance: Undecided
         Status: New

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

Title:
  glance-registry searches for [pipeline:glance-registry-<FLAVOR>]

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  Depending on what's in the flavor directive of /etc/glance/glance-
  registry.conf, glance-registry searches for a different section of
  /etc/glance/glance-registry-paste.ini. For example, if I put flavor =
  keystone+caching, then glance-registry searches for a section
  [pipeline:glance-registry-keystone+caching] in /etc/glance/glance-
  registry-paste.ini.

  If this is a feature, then the default configuration file should be
  updated to handle all values of the flavor directive.

  If it's a bug (eg: regression) and that glance-registry is searching
  for the wrong section, then this should be corrected.

  In the mean while, I'm patching the default configuration file in my
  Debian package to add the below lines to glance-registry-paste.ini:

  [pipeline:glance-registry-keystone]
  pipeline = osprofiler unauthenticated-context registryapp

  [pipeline:glance-registry-caching]
  pipeline = osprofiler unauthenticated-context registryapp

  [pipeline:glance-registry-keystone+caching]
  pipeline = osprofiler unauthenticated-context registryapp

  [pipeline:glance-registry-cachemanagement]
  pipeline = osprofiler unauthenticated-context registryapp

  [pipeline:glance-registry-keystone+cachemanagement]
  pipeline = osprofiler unauthenticated-context registryapp

  Without this, glance-registry may refuse to start by default, which is
  really annoying.

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