Bug 1386248

Summary:	Anaconda should remove /tmp/ks-script-* files
Product:	Red Hat Enterprise Linux 7	Reporter:	Jan Stodola <jstodola>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.3
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-15 07:47:17 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:
Bug Depends On:
Bug Blocks:	1256306

Description Jan Stodola 2016-10-18 13:35:27 UTC

Description of problem:
Anaconda creates ks-script-* files in /mnt/sysimage/tmp/ containing %post scripts from kickstart. When the installation is finished, anaconda doesn't erase these files and leave them on the disk. Anaconda should clean temporary files when they are not needed any more. 
The problem is that in case of booting with the inst.nosave=all option, it's expected to have no installation log files or kickstart files stored on disk when the installation is finished, which is not the case because of this bug.

Version-Release number of selected component (if applicable):
RHEL-7.3
anaconda-21.48.22.93-1.el7

How reproducible:
always

Steps to Reproduce:
1. create a kickstart file containing a %post script section
2. run ks installation
3. when the installation is finished, do not boot the system, just mount the file systems on the disk (you can use rescue mode)

Actual results:
/tmp/ks-script-* files containing the content of %post scripts from the previous installation

Expected results:
/tmp/ks-script-* files are not present on installed system

Comment 2 RHEL Program Management 2020-12-15 07:47:17 UTC

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.