Bug 680623

Summary: IOError: [Errno 2] No such file or directory: '/mnt/sysimage/boot/grub/grub.conf'
Product: [Fedora] Fedora Reporter: Andre Robatino <robatino>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 15CC: anaconda-maint-list, bos, jonathan, vanmeeuwen+fedora
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: anaconda_trace_hash:4cb8b8e97608c69e81cf4c7ca8b5e4bbbc5a2b1cdc0b554f59644149b4de3d18
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-19 14:59:23 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
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda. none

Description Andre Robatino 2011-02-26 14:33:58 UTC
The following was filed automatically by anaconda:
anaconda 15.20.1 exception report
Traceback (most recent call first):
  File "/usr/lib/python2.7/site-packages/pyanaconda/booty/x86.py", line 261, in writeGrubConf
    f = open(cf, "w+")
  File "/usr/lib/python2.7/site-packages/pyanaconda/booty/x86.py", line 227, in writeGrub
    cfPath)
  File "/usr/lib/python2.7/site-packages/pyanaconda/booty/x86.py", line 528, in write
    not self.useGrubVal)
  File "/usr/lib/python2.7/site-packages/pyanaconda/bootloader.py", line 217, in writeBootloader
    kernelList, otherList, defaultDev)
  File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 211, in moveStep
    rc = stepFunc(self.anaconda)
  File "/usr/lib/python2.7/site-packages/pyanaconda/dispatch.py", line 130, in gotoNext
    self.moveStep()
  File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1257, in nextClicked
    self.anaconda.dispatch.gotoNext()
  File "/usr/lib/python2.7/site-packages/pyanaconda/iw/progress_gui.py", line 79, in renderCallback
    self.intf.icw.nextClicked()
  File "/usr/lib/python2.7/site-packages/pyanaconda/gui.py", line 1278, in handleRenderCallback
    self.currentWindow.renderCallback()
IOError: [Errno 2] No such file or directory: '/mnt/sysimage/boot/grub/grub.conf'

Comment 1 Andre Robatino 2011-02-26 14:34:04 UTC
Created attachment 481147 [details]
Attached traceback automatically from anaconda.

Comment 2 Andre Robatino 2011-02-26 14:36:13 UTC
Seen while testing

https://fedoraproject.org/wiki/QA/TestCases/PartitioningExt4OnNativeDevice

Comment 3 Chris Lumens 2011-02-27 03:13:05 UTC
Are you doing something strange like installing over top an already installed system?  There's some messages like this that are puzzling:

[2011-02-26 09:15:40,860] WARN    : Package 1:grub-0.97-71.fc15.i686 already installed and latest version

Comment 4 Andre Robatino 2011-02-27 07:31:20 UTC
I don't remember exactly what the conditions were, but yes, I was doing repeated installs in a test VM and am pretty sure that was the case. I also saw another instance where it claimed there were file conflicts and wouldn't start installing packages (even though this was a fresh RC2 DVD install with no external repos enabled), but that wasn't reproducible either after I started with a fresh VM.

Comment 5 Chris Lumens 2011-03-10 16:01:06 UTC
We really shouldn't be allowing not formatting /.  I think there's already a bug for that, though I can't find it offhand.

Comment 6 Bryan O'Sullivan 2011-04-19 04:07:04 UTC
Created attachment 493069 [details]
Attached traceback automatically from anaconda.

Comment 7 Bryan O'Sullivan 2011-04-19 04:09:42 UTC
Wait, what's wrong with not formatting /? I have exactly a situation where I need to save / because that's where /home is, and I need to do an install because my previous attempt at an install failed and left the system in a mess. Surely that's not uncommon???

Comment 8 Chris Lumens 2011-04-19 14:59:23 UTC
With an unformatted /, you're going to have all the old libraries and config files laying around.  None of the old packages' contents will be removed, but I think the RPM db entries will be screwed up by the reinstall.  So you'll have a lot of stuff laying around cluttering the system that you can't really do anything about.

Then, the config files are going to create problems during installation.  Really, it's just best to start with a fresh system.  It's unfortunate about the /home problem, but that's why you should make it as a separate partition or LV.  It's true we did not used to set that up in the default partitioning but that's really only because we were busy arguing about how best to divy up the space.  You will need to do a backup.