Bug 149690 - kickstart.py removes /tmp/ks.cfg.new when %installclass used
Summary: kickstart.py removes /tmp/ks.cfg.new when %installclass used
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda   
(Show other bugs)
Version: 3.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Paul Nasrat
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2005-02-25 10:26 UTC by David Lehman
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-27 17:20:05 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Don't remove /tmp/ks.cfg.new (330 bytes, patch)
2005-02-25 10:26 UTC, David Lehman
no flags Details | Diff

Description David Lehman 2005-02-25 10:26:22 UTC
Created attachment 111421 [details]
Don't remove /tmp/ks.cfg.new

Comment 1 David Lehman 2005-02-25 10:26:22 UTC
Description of problem:
When defining a custom installclass in the ks.cfg, the Kickstart method unlinks
the ks.cfg.new long before setInstallData (hence also readKickstart) is called.
This, of course, leads to a traceback when readKickstart tries to open the
long-gone file.

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

How reproducible:

Steps to Reproduce:
1. define a basic subclass of KickstartBase using %installclass in ks.cfg
2. try to use it
Actual results:
Traceback - I can get the exact traceback on request, but all you need to do is
look at the code and you'll see it.

Expected results:
No traceback

Additional info:

Comment 2 Jeremy Katz 2005-03-14 16:57:27 UTC
FWIW, I wouldn't recommend counting on this functionality.  It's undocumented
from what I remember and very likely to go away (I know for a fact that it's
never tested :)

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