yahoo-eng-team team mailing list archive

[Ian Cordasco <icordasc+launchpad@xxxxxxxxxx>]

The switch to oslo_log from glance/openstack/common/log.py is not going
to be backported to stable/juno, no. This is definitely something I have
heard of people encountering before (and I'm frankly surprised there
wasn't already a bug for it).

** Changed in: glance
       Status: New => Triaged

** Also affects: glance/juno
   Importance: Undecided
       Status: New

** Changed in: glance/juno
       Status: New => Triaged

** Changed in: glance/juno
   Importance: Undecided => High

** Changed in: glance
       Status: Triaged => Invalid

-- 
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):
  Invalid
Status in Glance juno series:
  Triaged

Bug description:
  With syslog enabled on Juno (use_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