Bug 1784012

Summary:	Default kickstart places log to /mnt/sysimage/root/install.post.log
Product:	Red Hat Satellite	Reporter:	roarora
Component:	Provisioning Templates	Assignee:	Lukas Zapletal <lzap>
Status:	CLOSED ERRATA	QA Contact:	Roman Plevka <rplevka>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.6.0	CC:	aeladawy, ahumbe, ajambhul, anerurka, anrussel, bo.neace, dhjoshi, ldixon, lzap, mcasabur, mhulan, mmccune, sadas, tim.daley
Target Milestone:	6.8.0	Keywords:	EasyFix, PrioBumpGSS, Regression, Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:	needs
Fixed In Version:	foreman-2.1.2.9-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 12:59:35 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 roarora 2019-12-16 13:51:28 UTC

Description of problem:

In %post section we are already in chrooted environment. So --log /mnt/sysimage/root/install.post.log will create log file with this path in the actual OS file structure.

It should be directing logs to /root/install.post.log as we did prior.


Version-Release number of selected component (if applicable):
Satelliet 6.6

How reproducible:
Always

Steps to Reproduce:
1. Provision a system with satellite 6
2. Post logs are in /mnt/sysimage/root/install.post.log instead of /root/install.post.log



Expected results:
provisioning template should not hould not be creating logging files under /mnt

Additional info:

Comment 5 Bryan Kearney 2019-12-17 09:05:10 UTC

Upstream bug assigned to lzap

Comment 7 Lynn Dixon 2020-03-31 15:25:04 UTC

Just to add another data point, I was able to duplicate this in my lab very easily.  I am using Sat 6.6 and standard kickstart templates, and PXE provisioned a normal RHEL 7.7 guest and this is the results after the machine was provisioned:  
https://share.getcloudapp.com/RBudj5r2


Adding myself to this BZ as well so I can keep a customer updated on its status.  I'm happy to help test in my lab.

Comment 8 rhituser 2020-03-31 16:25:02 UTC

It appears that this file is severely limited in terms of its usefulness when compared to previous information stored within this file.  From what I'm seeing, it's missing the majority of its previous contents such as Subscription Manager registration and other snippet output (Katello agent package install information, etc) and yum update logging information.  Easily, less than perhaps a tenth of the typical information as previously seen is contained within this log file now.  With this said, there is a bigger issue than this log file simply not being placed in root's home directory.  This lack of log detail was noticed on a recent RHEL 8.1 and 7.7 server.

Comment 9 Lukas Zapletal 2020-04-01 09:44:45 UTC

Hello, some of the logging is now redirected into /root/install.postnochroot.log - check that file.

Comment 12 Lukas Zapletal 2020-08-11 11:35:30 UTC

WORKAROUND: Use the following template change: https://gitlab.sat.engineering.redhat.com/satellite6/foreman/-/merge_requests/520/diffs

Comment 14 Lukas Zapletal 2020-08-25 07:37:58 UTC

Hello, any version. It is one line change.

Comment 18 Roman Plevka 2020-09-21 13:16:55 UTC

VERIFIED
on sat6.8.0-16

the install.post.log is correctly placed inside /root/ directory now.

Comment 22 errata-xmlrpc 2020-10-27 12:59:35 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4366