Description of problem: Version-Release number of selected component: anaconda-18.6.4 Additional info: libreport version: 2.0.12 cmdline: initrd=initrd.img quiet rd.live.check BOOT_IMAGE=vmlinuz kernel: 3.6.0-0.rc2.git2.1.fc18.i686
Created attachment 610188 [details] File: ifcfg.log
Created attachment 610189 [details] File: anaconda-tb
Created attachment 610190 [details] File: environ
Created attachment 610191 [details] File: type
Created attachment 610192 [details] File: storage.log
Created attachment 610193 [details] File: version
Created attachment 610194 [details] File: program.log
Created attachment 610195 [details] File: product
Created attachment 610196 [details] File: syslog
Created attachment 610197 [details] File: hashmarkername
Created attachment 610198 [details] File: anaconda.log
Created attachment 610199 [details] File: release
Created attachment 610200 [details] File: description
I created 3.9 GB disk, opened Storage spoke, selected my disk, hit Back and this error appeared. F18 Alpha TC5 netinst
Proposing as Alpha blocker: " The installer must be able to complete an installation using any locally connected storage interface (e.g. PATA, SATA, SCSI etc...) with the default file system " https://fedoraproject.org/wiki/Fedora_18_Alpha_Release_Criteria
I'm not sure this is really a bug. I don't believe 3.9GB is enough space for a standard net install. Did you check with F17 to see what happens? I suspect you can't do a standard net install to a 3.9GB disk with F17 either. Though there should be a 'nice' error message, not any kind of crash.
I tried F17 netinst with the same disk and I can install minimal package set just fine. But that's not the point of this bug, at least not the intended point (I'm sure some people will complain about this). The installer shouldn't crash and should display a reasonable message. I am able to find and read the crash from the traceback message, but the general users won't be. And it might be quite frequent that someone creates a VM with a too small disk and tries to install Fedora on it. Of course, this doesn't have to block Alpha exactly, but it should block something.
Error handling is in the works and should be getting pushed pretty soon.
I vote -1 blocker; this is annoying if you have a too-small disk, but not really severe enough to block release. I guess it'd be a conditional infringement of "The installer must be able to complete an installation using any locally connected storage interface (e.g. PATA, SATA, SCSI etc...) with the default file system", in the case that the disk is too small, I vote -1 on the basis that the affected case isn't serious enough.
-1 Blocker +1 NTH
-blocker + NTH
that's three -1/+1s, so rejecting as blocker, accepting as NTH.
*** Bug 855479 has been marked as a duplicate of this bug. ***
Re-proposing as F18 Final Blocker.
(In reply to comment #14) > I created 3.9 GB disk, opened Storage spoke, selected my disk, hit Back and > this error appeared. > > F18 Alpha TC5 netinst Can you clarify whether you selected software before going into the storage spoke? I can't reproduce your steps here.
(In reply to comment #25) > Can you clarify whether you selected software before going into the storage > spoke? > > I can't reproduce your steps here. No I haven't. I went straight to the Storage spoke and back. But If I select minimal install first and go to Storage second, it crashes as well. F18 Alpha RC2 i686 netinst
(In reply to comment #26) > (In reply to comment #25) > > Can you clarify whether you selected software before going into the storage > > spoke? > > > > I can't reproduce your steps here. > > No I haven't. I went straight to the Storage spoke and back. But If I select > minimal install first and go to Storage second, it crashes as well. > > F18 Alpha RC2 i686 netinst See, that's odd. Because you haven't selected any software at first, we don't know what size you'll need, so we shouldn't be able to do a size check. Can you attach a fresh set of logs from doing a direct to storage spoke and back getting the crash with the latest images? Thanks!
(In reply to comment #27) > (In reply to comment #26) > > (In reply to comment #25) > > > Can you clarify whether you selected software before going into the storage > > > spoke? > > > > > > I can't reproduce your steps here. > > > > No I haven't. I went straight to the Storage spoke and back. But If I select > > minimal install first and go to Storage second, it crashes as well. > > > > F18 Alpha RC2 i686 netinst > > See, that's odd. Because you haven't selected any software at first, we > don't know what size you'll need, so we shouldn't be able to do a size check. > > Can you attach a fresh set of logs from doing a direct to storage spoke and > back getting the crash with the latest images? Thanks! Disregard. I misread the error. The error is saying that the partitions you've requested won't actually fit in the space you have available on your disks. Are you removing the existing partitions first? We know that the error catching is not optimal for Alpha, but this really does look like a case of just requesting partitions that won't fit.
This is a completely empty disk (just created), just very small. Auto-partitioning requested (I haven't entered the manual partitioning screen). I have 1500 MB RAM assigned to that VM, maybe you try to create 3 GB of swap? Then it wouldn't fit even for minimal install.
(In reply to comment #29) > This is a completely empty disk (just created), just very small. > Auto-partitioning requested (I haven't entered the manual partitioning > screen). I have 1500 MB RAM assigned to that VM, maybe you try to create 3 > GB of swap? Then it wouldn't fit even for minimal install. It is still the case that you will need to use custom partitioning if you have such limited disk space. 10GB should be plenty for automatic partitioning.
(In reply to comment #30) > It is still the case that you will need to use custom partitioning if you > have such limited disk space. 10GB should be plenty for automatic > partitioning. Let's say this to the user in a pretty error dialog instead of crashing the installer :-)
(In reply to comment #31) > (In reply to comment #30) > > It is still the case that you will need to use custom partitioning if you > > have such limited disk space. 10GB should be plenty for automatic > > partitioning. > > Let's say this to the user in a pretty error dialog instead of crashing the > installer :-) Error handling is waiting for the first post-alpha build. I only wrote that commend because it sounded like you were complaining that we don't modify our automatic partitioning algorithm based on your choice of disk size.
I see this when trying to install to a 4 GB USB from RC1 desktop live. I get error message after selecting it with autopartition. No message warning of too small a disk. Just that it will not install. 8 GB USB installs correctly. Unable to select non LVM format with just ext4 ( / ) as swap is not healthy for use with a USB
(In reply to comment #33) > I see this when trying to install to a 4 GB USB from RC1 desktop live. I get > error message after selecting it with autopartition. No message warning of > too small a disk. Just that it will not install. 8 GB USB installs > correctly. Unable to select non LVM format with just ext4 ( / ) as swap is > not healthy for use with a USB Note does not crash just will not install
I have tried the original reproducer with F18 Beta and this is fixed, anaconda doesn't crash, it displays "new lv is too large to fit in free space" error, which is more or less understandable. While trying this, it is _extremely easy_ to trigger bug 867770. Also, the whole dialog that states how much space is required and the error dialog should be overhauled, but that's not part of this particular bug. This crash is fixed now.