Glance-manage should log to a unique file
Bug #1391211 reported by
Matt Kassawara
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
High
|
Ian Cordasco |
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)
Changed in glance: | |
importance: | Undecided → High |
Changed in glance: | |
assignee: | nobody → Ian Cordasco (icordasc) |
status: | Confirmed → In Progress |
milestone: | none → kilo-1 |
Changed in glance: | |
status: | Fix Committed → Fix Released |
Changed in glance: | |
milestone: | kilo-1 → 2015.1.0 |
To post a comment you must log in.
I suspect that this is because we use glance-registry and glance-api's config files (https:/ /github. com/openstack/ glance/ blob/453706b4b3 a3d6d9c3b154a1f de59c34fc30234b /glance/ cmd/manage. py#L267. .L270) to configure glance-manage even though there's apparently the ability to have a glace-manage.conf file (https:/ /github. com/openstack/ glance/ blob/453706b4b3 a3d6d9c3b154a1f de59c34fc30234b /etc/oslo- config- generator/ glance- manage. conf). Even if a glance-manage.conf file existed, it wouldn't be used at this point. I'm going to look to see how other services manage to have separate logs for this without having their own -manage.conf files.