Bug 810351

Summary: RuntimeError: Error running mkofboot: No such file or directory
Product: [Fedora] Fedora Reporter: Karsten Hopp <karsten>
Component: loraxAssignee: Martin Gracik <mgracik>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: 17CC: bcl, dmach, g.kaviyarasu, jonathan, kmonroe, knight, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: powerpc   
OS: Linux   
Whiteboard: abrt_hash:c30888e46e234aca2e78a7ec90f0fe3e72219e1462658a44e90f264aa71a70c5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-20 16:21:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: anaconda-tb-2Q1z6a none

Description Karsten Hopp 2012-04-05 17:03:15 UTC
libreport version: 2.0.8
cmdline:        /usr/bin/python  /usr/sbin/anaconda
executable:     /usr/sbin/anaconda
exnFileName:    /tmp/anaconda-tb-2Q1z6a
hashmarkername: anaconda
kernel:         3.3.0-1.fc17.ppc64
other involved packages: 
product:        Fedora
reason:         RuntimeError: Error running mkofboot: No such file or directory
release:        Cannot get release name.
time:           Do 05 Apr 2012 19:01:56 CEST
version:        17

anaconda-tb-2Q1z6a: Text file, 428097 bytes

description:
:The following was filed automatically by anaconda:
:anaconda 17.18 exception report
:Traceback (most recent call first):
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/iutil.py", line 181, in execWithRedirect
:    raise RuntimeError, errstr
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1932, in install
:    root=ROOT_PATH)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 1091, in write
:    self.install()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/bootloader.py", line 2344, in writeBootloader
:    anaconda.bootloader.write()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 383, in dispatch
:    self.dir = self.steps[self.step].target(self.anaconda)
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/text.py", line 507, in run
:    self.anaconda.dispatch.dispatch()
:  File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 326, in run
:    self.anaconda.intf.run(self.anaconda)
:  File "/usr/sbin/anaconda", line 852, in <module>
:    anaconda.dispatch.run()
:RuntimeError: Error running mkofboot: No such file or directory

environ:
:LANG=de_DE.UTF-8
:LC_NUMERIC=C
:TERM=linux
:XAUTHORITY=/root/.Xauthority
:GLADEPATH=/tmp/updates/:/tmp/updates/data/ui/:ui/:/usr/share/anaconda/ui/:/usr/share/python-meh/
:SHLVL=0
:PYTHONPATH=/tmp/updates
:LIBUSER_CONF=/tmp/libuser.FYXTni
:LVM_SUPPRESS_FD_WARNINGS=1
:PWD=/
:MALLOC_PERTURB_=204
:GCONF_GLOBAL_LOCKS=1
:HOME=/tmp
:PIXMAPPATH=/tmp/updates/pixmaps/:/tmp/updates/:/tmp/product/pixmaps/:/tmp/product/:pixmaps/:/usr/share/anaconda/pixmaps/:/usr/share/pixmaps/:/usr/share/anaconda/:/usr/share/python-meh/:/usr/share/icons/Fedora/48x48/apps/
:PATH=/usr/bin:/bin:/sbin:/usr/sbin:/mnt/sysimage/bin:/mnt/sysimage/usr/bin:/mnt/sysimage/usr/sbin:/mnt/sysimage/sbin:/sbin:/usr/sbin
:MALLOC_CHECK_=2

Comment 1 Karsten Hopp 2012-04-05 17:03:22 UTC
Created attachment 575498 [details]
File: anaconda-tb-2Q1z6a

Comment 2 Brian Lane 2012-04-09 17:21:19 UTC
yaboot provides mkofboot, it is a symlink to ybin, are either of those present? The yaboot.spec shows:

/boot/efika.forth
/sbin/ofpath
/sbin/ybin
/sbin/yabootconfig
/sbin/mkofboot
/usr/lib/yaboot/addnote
/usr/lib/yaboot/ofboot
/usr/lib/yaboot/yaboot
/usr/lib/yaboot/yaboot.debug

Are all of those there?

Comment 3 Brian Lane 2012-04-12 14:31:49 UTC
*** Bug 811972 has been marked as a duplicate of this bug. ***

Comment 4 Karsten Hopp 2012-04-12 15:02:56 UTC
We've switched to grub2 on PPC, so yaboot shouldn't be installed at all. Grub2 works fine on IBM Power systems, it is just on PowerMac where this problem shows up due to the way the firmware works. I'll try to figure out what needs to be chenged in anaconda. It can be done, as I've had reports that even G4 machines can be booted with grub2.

Comment 5 Karsten Hopp 2013-01-20 16:21:50 UTC
I haven't seen this issue again for quite a while now, so we can safely assume that this has been fixed