yahoo-eng-team team mailing list archive

[Matt Kassawara <mkassawara@xxxxxxxxx>]

Public bug reported:

The glance-manage utility (particularly the database sync operation)
writes to the API log instead of a unique file such as glance-
manage.log. In a typical environment, the glance-manage utility runs as
root and creates the API log with root ownership. The glance-api service
generally runs as the glance user and won't start because it can't write
to the API log. The *-manage utility included with most other services
already uses *-manage.log which prevents this issue.

Version: 2014.2 (also affects earlier versions)

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

Title:
  Glance-manage should log to a unique file

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

Bug description:
  The glance-manage utility (particularly the database sync operation)
  writes to the API log instead of a unique file such as glance-
  manage.log. In a typical environment, the glance-manage utility runs
  as root and creates the API log with root ownership. The glance-api
  service generally runs as the glance user and won't start because it
  can't write to the API log. The *-manage utility included with most
  other services already uses *-manage.log which prevents this issue.

  Version: 2014.2 (also affects earlier versions)

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