Bug 165865

Summary: [PATCH] loader can't parse kickstart correctly when %pre, %post, or %packages have options/args
Product: Red Hat Enterprise Linux 3 Reporter: David Lehman <dlehman>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED ERRATA QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: tao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHEA-2006-0150 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-15 15:33:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 168424    
Attachments:
Description Flags
fix loader's parsing of kickstart none

Description David Lehman 2005-08-12 21:47:23 UTC
Created attachment 117698 [details]
fix loader's parsing of kickstart

Comment 1 David Lehman 2005-08-12 21:47:23 UTC
Description of problem:
The part of loader that parses the kickstart for commands will continue parsing
throughout the %pre/%post/%package sections until one of them doesn't have any
options. This is because in ksReadCommands it strips leading and trailing
whitespace but then checks for the *exact* strings, not just initial substrings.

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

How reproducible:
Always

Steps to Reproduce:
1. Put a python script as a %pre right after the commands section of ks.cfg 
2. make sure you assign to a variable called 'url' in the python script
3.
  
Actual results:
A customer claimed they got a newt error dialog, I just got a hung loader

Expected results:
No problems

Additional info:

Comment 7 Red Hat Bugzilla 2006-03-15 15:33:15 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2006-0150.html