Bug 241878 - Anaconda raise a traceback if the %pre or %post script remove itself from /tmp
Anaconda raise a traceback if the %pre or %post script remove itself from /tmp
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Depends On:
  Show dependency treegraph
Reported: 2007-05-31 08:01 EDT by Klaus Ethgen
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-05-31 10:34:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Klaus Ethgen 2007-05-31 08:01:46 EDT
Description of problem:
Anaconda raise a traceback if the %pre or %post script remove itself from /tmp. 
This might be needed if one has to clean up the /tmp at the end of %post for 
leaving a clean one.

How reproducible:
# Doing some stuff here
rm -fr /tmp/* /tmp/.??*

Actual results:
A traceback in anaconda

Expected results:
Maybe a warning but nothing more

Additional info:
I know that I can use "--nochroot" but anaconda should not be so fragil.
Comment 1 Chris Lumens 2007-05-31 09:19:13 EDT
Please attach the complete traceback to this bug report.
Comment 2 Klaus Ethgen 2007-05-31 10:21:52 EDT
I would be happy to do so but I do not know how to save such a traceback in the 
kickstart process. Also cut and paste do not work as there is no other terminal 
when anaconda halted the system.

I wrote down the message before the halt: "OSError: [Error 2] No such file or 
directory: '/mnt/sysimage/tmp/ks-script-xuAsIT'"
Comment 3 Chris Lumens 2007-05-31 10:34:15 EDT
This will be fixed in the next release of RHEL.  If you require this fix in an
update release, please speak to your support representative who will raise it
through the appropriate channels.  Thanks for the bug report.

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