Bug 1428572

Summary:	Nova Cannot write to /var/log/nova/nova-manage.log on Undercloud
Product:	Red Hat OpenStack	Reporter:	Chris Paquin <cpaquin>
Component:	puppet-nova	Assignee:	Ollie Walsh <owalsh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10.0 (Newton)	CC:	aschultz, berrange, bschmaus, dasmith, eglynn, jjoyce, jschluet, kchamart, lyarwood, marjones, mbooth, mburns, mmethot, mschuppe, nlevinki, owalsh, rhel-osp-director-maint, sbauza, sferdjao, sgordon, slinaber, srevivo, tvignaud, vromanso
Target Milestone:	async	Keywords:	Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	puppet-nova-9.6.0-4.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-07-16 11:27:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.