Red Hat Bugzilla – Bug 241395
FC6 -> F7 anaconda upgrade traceback
Last modified: 2013-09-02 02:20:44 EDT
# RPM anaconda-184.108.40.206-1.x86_64.rpm
# ARCH x86_64
Probing for video card: nVidia Corporation NV44 [Quadro NVS 285]
Traceback (most recent call last):
File "/usr/bin/anaconda", line 949, in <module>
File "/usr/lib/anaconda/kickstart.py", line 1056, in setSteps
AttributeError: 'bool' object has no attribute 'setSteps'
Attaching anaconda-logs.tgz (not the tmp/anaconda.log includes several attempts
to recreate the failure in order to capture the output)
(~)> tar -ztvf ~/Desktop/anaconda-logs.tgz
-rw-r--r-- root/root 23134 2007-06-01 20:58:34 tmp/syslog
-rw-r--r-- root/root 65056 2007-06-01 21:16:35 tmp/anaconda.log
-rw------- root/root 1017 2007-06-01 21:15:19 tmp/ks.cfg
-rw-r--r-- root/root 338 2007-06-01 21:16:35 tmp/trace.txt
I believe this is the RC2 tree (.treeinfo below):
family = Fedora
timestamp = 1180061782.66
variant = Fedora
totaldiscs = 1
version = 7
discnum = 1
packagedir = Fedora
arch = x86_64
Created attachment 155469 [details]
Fixed in head, and I think we're going to pull this into an updates.img.
I'm hitting this - is the updates.img available?
This bug is now addressed by an updates image. It is available for download at:
Instructions for using updates disks are located at:
If possible, please test this image out and report if it fixes your issue or
not. Once we are confident that your issue is solved by this image, we are
going to announce it more publicly. This fix may also be included in an updated
anaconda package later for people who are making custom Fedora distributions.
Thanks for your time.
update bombs with:
/tmp/updates/kickstart.py line 30
import pykickstart.commands as commands
ImportError: No module named commands
Thanks for the report. Please try it now.
Anaconda starts up okay, but then it asks how I want to partition the disk
rather than upgrading the existing install.
Sounds like anaconda is not detecting your existing installation and therefore
doesn't give you the option of install vs. upgrade. What's your layout? What's
in the anaconda log files? This may be better served with a different bug, in fact.
Opened bug #243159 for the upgrade issue.
Any chance that the anaconda fixes for this will be released as a F7 update so
that respins of an updated F7 work?
I've committed the fixes in the updates.img to the F7 branch of anaconda. We'll
probably build a new one in a few weeks to give more time to see what are the
really common bugs. Then, anyone who wants to make a new F7 can take advantage
of the fixes.
*** Bug 248596 has been marked as a duplicate of this bug. ***
*** Bug 253227 has been marked as a duplicate of this bug. ***
I am trying to do a kickstart upgrade from a custom FC6 to a custom FC7 distro.
After encountering the known issue (line 949), I downloaded the f7-updates.img
file, renamed it to updates.img and put it under the images/ folder of my custom
distro cd. The installer then continues till it displays the 'transferring
install image to harddrive' message. I then get the error show below. Is it at
all possible to use the updates like this (in the images/ folder of the cd), as
the wiki states that is is possible to do this with network install.
Traceback (most recent call first):
File "/tmp/treedir.27118/instimage/usr/lib/anaconda/isys.py", line 244, in
File "/usr/lib/anaconda/image.py", line 188, in systemMounted
File "/tmp/treedir.27118/instimage/usr/lib/anaconda/yuminstall.py", line 1107,
if self.method.systemMounted (anaconda.id.fsset, anaconda.rootPath):
File "/tmp/treedir.27118/instimage/usr/lib/anaconda/backend.py", line 230, in
File "/usr/lib/anaconda/dispatch.py", line 203, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
File "/usr/lib/anaconda/text.py", line 605, in run
File "/tmp/updates/anaconda", line 955, in <module>
SystemError: (6, 'No such device or address')