Bug 1428572 - Nova Cannot write to /var/log/nova/nova-manage.log on Undercloud
Summary: Nova Cannot write to /var/log/nova/nova-manage.log on Undercloud
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-nova
Version: 10.0 (Newton)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: async
: 10.0 (Newton)
Assignee: Ollie Walsh
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-02 20:57 UTC by Chris Paquin
Modified: 2022-08-09 14:09 UTC (History)
24 users (show)

Fixed In Version: puppet-nova-9.6.0-4.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-16 11:27:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1671681 0 None None None 2017-03-10 03:02:30 UTC
OpenStack gerrit 498723 0 None MERGED Correct permissions on the nova logfiles 2021-01-13 11:58:50 UTC
OpenStack gerrit 561695 0 None MERGED Correct permissions on the nova logfiles 2021-01-13 11:59:28 UTC
OpenStack gerrit 561742 0 None MERGED Correct permissions on the nova logfiles 2021-01-13 11:59:29 UTC
Red Hat Bugzilla 1044155 0 unspecified CLOSED openstack-db command is too aggressive about redirecting stderr 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1289761 0 low CLOSED PackStack installs Nova crontab that nova user can't run 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1368588 0 low CLOSED [abrt] openstack-nova-common: __init__.py:925:_open:IOError: [Errno 13] Permission denied: '/var/log/nova/nova-manage.lo... 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker OSP-8554 0 None None None 2022-08-09 14:09:51 UTC
Red Hat Knowledge Base (Solution) 3498911 0 None None None 2018-06-26 18:28:02 UTC

Internal Links: 1044155 1289761 1368588

Description Chris Paquin 2017-03-02 20:57:56 UTC
Description of problem:

[stack@tpavcpusituc1 templates]$ sudo abrt-cli ls
id 09b80970207c2ec34359bf3eb4e2fcecce870111
reason:         __init__.py:925:_open:IOError: [Errno 13] Permission denied: '/var/log/nova/nova-manage.log'
time:           Thu 16 Feb 2017 12:01:03 AM EST
cmdline:        /usr/bin/python2 /bin/nova-manage db archive_deleted_rows --max_rows 100
package:        openstack-nova-common-14.0.2-7.el7ost
uid:            162 (nova)
count:          15
Directory:      /var/spool/abrt/Python-2017-02-16-00:01:03-25684
Run 'abrt-cli report /var/spool/abrt/Python-2017-02-16-00:01:03-25684' for creating a case in Red Hat Customer Portal



Version-Release number of selected component (if applicable):
OSP 10 Undercloud

How reproducible:
Deploy OSP 10 undercloud, become root, run abrt-cli ls

Steps to Reproduce:
1.
2.
3.

Actual results:
Log owned by root

-rw-r--r--. 1 root root 215298 Feb 15 12:11 /var/log/nova/nova-manage.log


Expected results:
Nova should have ability to write to log

Additional info:

Comment 1 Chris Paquin 2017-03-02 20:59:22 UTC
The command being run is 

1 0 * * * nova-manage db archive_deleted_rows --max_rows 100 >>/dev/null 2>&1


This is being run from nova's crontab -see below

[root@tpavcpusituc1 cron]# cat nova 
# HEADER: This file was autogenerated at 2017-02-15 12:11:41 -0500 by puppet.
# HEADER: While it can still be managed manually, it is definitely not recommended.
# HEADER: Note particularly that the comments starting with 'Puppet Name' should
# HEADER: not be deleted, as doing so could cause duplicate cron jobs.
# Puppet Name: nova-manage db archive_deleted_rows
PATH=/bin:/usr/bin:/usr/sbin SHELL=/bin/sh
1 0 * * * nova-manage db archive_deleted_rows --max_rows 100 >>/dev/null 2>&1

Comment 2 Benjamin Schmaus 2017-05-11 01:12:11 UTC
Hey Diana - Any update on the status of fixing this issue or when customer might see the errata.  The customer has worked around the permission issue but it would be nice to get it resolved.

Comment 3 Chris Fields 2017-06-12 14:42:48 UTC
Can I get an update on the status of this bug?  I need to update the a customers support case.


Note You need to log in before you can comment on or make changes to this bug.