Bug 57600 - kickstart lilocheck command broken - was Syntax error in /usr/lib/anaconda/kickstart.py
kickstart lilocheck command broken - was Syntax error in /usr/lib/anaconda/ki...
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-12-17 08:39 EST by Ton Kersten
Modified: 2007-04-18 12:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-12-17 11:55:08 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ton Kersten 2001-12-17 08:39:09 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4)
Gecko/20011126 Netscape6/6.2.1

Description of problem:
In the program /usr/lib/anaconda/kickstart.py there is a syntax error in 
line 264. This lines states: "def LiloCheck(self, args):"
But when we try to run a kickstart install this lines gives us an error.
After changing this line to "def LiloCheck(self, id, args):" and rebuilding
the stage2.img (mkcramfs) everything worked oke.

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


How reproducible:
Always

Steps to Reproduce:
1.Create a kickstart install server
2.Start to install a machine with "lilocheck" on in the kickstart file
3.
	

Actual Results:  The kickstart installer crashed and the install could not
be completed.

Expected Results:  The machine should have continued with the installation
and installation should complete successfully.

Additional info:
Comment 1 Michael Fulbright 2001-12-17 11:55:03 EST
Thanks for the patch!
Comment 2 Jeremy Katz 2001-12-17 11:59:45 EST
Fixed in CVS

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