Bug 253227

Summary: Installer crashes in kickstart.py script on line1056 when performing a kickstart upgrade
Product: [Fedora] Fedora Reporter: Gunter Woytowitz <gunter.woytowitz>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: medium    
Version: 7   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-08-17 14:32:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Gunter Woytowitz 2007-08-17 14:28:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; InfoPath.1; .NET CLR 2.0.50727)

Description of problem:
When performing an kickstart upgrade from a CDROM the install crashses in the kickstart.py script. 

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

How reproducible:

Steps to Reproduce:
1.Boot with this command

boot: linux ks=cdrom:/ks.cfg

2. Using the following ks.cfg file
nfs --server= --dir=/export/fc7/ISO
lang en_US.UTF-8
keyboard us
network --device eth0 --bootproto dhcp

Actual Results:
I get the following error

 File "/usr/lib/anaconda", line 949, in <module>
 File "/usr/lib/anaconda/kickstart.py", line 1056, in setSteps
AttributeError: 'bool' object has no attribute 'setSteps'
install exited abnormally [1/1]

Expected Results:
Should successfully upgrade!!

Additional info:
If I change the ks.cfg file to be an "install" instead of an "upgrade" with similar settings everything works fine.

Here's a snippet of the kickstart.py code line 949 is the problem.
945:    interactive = ksdata.interactive.interactive
946:    upgrade = ksdata.upgrade.upgrade
948:    if upgrade:
949:        upgrade.setSteps(anaconda)
951:        # we have no way to specify migrating yet

It does appear that the upgrade variable is just a boolean, so I'm not sure how any upgrade would ever work????

Comment 1 Chris Lumens 2007-08-17 14:32:07 UTC

*** This bug has been marked as a duplicate of 241395 ***