← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1422317] [NEW] Juno glance spins with use_syslog=True

 

Public bug reported:

With syslog enabled on Juno (enable_syslog=True in glance-api.conf),
glance spins on startup, consuming all available CPU cycles.

With some carefully placed calls to exit(), the line in glance causing
the problem was determined to be
https://github.com/openstack/glance/blob/stable/juno/glance/openstack/common/log.py#L523.
After this point the code gets lost in logging.handlers.SyslogHandler().

I noticed that the <component>.openstack.common.log source file was
somewhat different in glance compared to several other OpenStack
components. An update to glance.openstack.common missed the juno branch
by a couple of commits
https://github.com/openstack/glance/commit/d4f890798a0588a80e21fad044d4df5d0964dc70.
Cherry picking this commit fixed the issue for me.

** 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/1422317

Title:
  Juno glance spins with use_syslog=True

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

Bug description:
  With syslog enabled on Juno (enable_syslog=True in glance-api.conf),
  glance spins on startup, consuming all available CPU cycles.

  With some carefully placed calls to exit(), the line in glance causing
  the problem was determined to be
  https://github.com/openstack/glance/blob/stable/juno/glance/openstack/common/log.py#L523.
  After this point the code gets lost in
  logging.handlers.SyslogHandler().

  I noticed that the <component>.openstack.common.log source file was
  somewhat different in glance compared to several other OpenStack
  components. An update to glance.openstack.common missed the juno
  branch by a couple of commits
  https://github.com/openstack/glance/commit/d4f890798a0588a80e21fad044d4df5d0964dc70.
  Cherry picking this commit fixed the issue for me.

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


Follow ups

References