When you execute nova-manage commands, oslo logs to the following
location (file name is dynamically created based on command name).
/var/log/nova/nova-manage.log
Because puppet-nova is executing these commands as root,
nova-manage.log is owned by root, preventing the 'nova-manage
db archive_deleted_rows' entry in nova's crontab from executing.
This log file is also an outlier, as all other log files in
/var/log/nova/ are owned by nova:nova.
Similar issues are possible for other nova logs, if for example
a nova services is initially started manually as root, so the
ownership of all nova logs is corrected before configuring nova.
Reviewed: https:/ /review. openstack. org/498723 /git.openstack. org/cgit/ openstack/ puppet- nova/commit/ ?id=e128ba6538e b806589ebc01c16 ee5e298bb0ee86
Committed: https:/
Submitter: Zuul
Branch: master
commit e128ba6538eb806 589ebc01c16ee5e 298bb0ee86
Author: Diana Clarke <email address hidden>
Date: Tue Mar 7 14:07:16 2017 -0500
Correct permissions on the nova logfiles
When you execute nova-manage commands, oslo logs to the following
location (file name is dynamically created based on command name).
Because puppet-nova is executing these commands as root, deleted_ rows' entry in nova's crontab from executing.
nova-manage.log is owned by root, preventing the 'nova-manage
db archive_
Permission denied: '/var/log/ nova/nova- manage. log'
This log file is also an outlier, as all other log files in
/var/log/nova/ are owned by nova:nova.
Similar issues are possible for other nova logs, if for example
a nova services is initially started manually as root, so the
ownership of all nova logs is corrected before configuring nova.
Co-Authored-By: Oliver Walsh <email address hidden> c79074cf603dcab 9135f96e765
Co-Authored-By: Diana Clarke <email address hidden>
Co-Authored-By: Maciej Kucia <email address hidden>
Closes-Bug: #1671681
Change-Id: I0ca0110cbf9139