Bug 863582

Created attachment 622477 [details]
File: ifcfg.log

Created attachment 622478 [details]
File: anaconda-tb

Created attachment 622479 [details]
File: environ

Created attachment 622480 [details]
File: type

Created attachment 622481 [details]
File: storage.log

Created attachment 622482 [details]
File: version

Created attachment 622483 [details]
File: program.log

Created attachment 622484 [details]
File: product

Created attachment 622485 [details]
File: anaconda.log

Created attachment 622486 [details]
File: hashmarkername

Created attachment 622487 [details]
File: cmdline_file

Created attachment 622488 [details]
File: release

Created attachment 622489 [details]
File: messages

Reproduced with:
1. Click "Installation Destination".
2. Click "Continue".

With Fedora-18-Nightly-20121003.08-x86_64-Live-desktop.iso in a VM.

The target was an empty VM disk image:
$ qemu-img create f18-test-3.img 10G
$ hexdump -C f18-test-3.img 
00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
280000000

$ qemu-kvm -m 2048 -hda f18-test-3.img -cdrom ~/xfr/fedora/nightly-composes/Fedora-18-Nightly-20121003.08-x86_64-Live-desktop.iso -usb -vga qxl -boot menu=on

Just picking an empty disk as an install target for a live install with anaconda 18.13.

Package: anaconda-18.13-1.fc18.x86_64
OS Release: Fedora release 18

note that, interestingly, you can simply go to the disk selection spoke, have a disk selected, and click 'Done' at top left, and it'll work - anaconda will go with autopart on that disk, assuming it has enough free space. you don't actually have to click 'Continue'. that seems a little strange from a UI perspective, but it works around this bug.

even with that workaround, this is obviously a beta blocker, it prevents access to custom partitioning or the 'help me free space' process, so it hits Alpha "The installer must be able to complete an installation using automatic partitioning to any sufficiently large target disk, whether unformatted, empty, or containing any kind of existing data".

I believe this bug actually happens _only_ if the target disk is empty (no partitions, I guess is the definition of 'empty' here.) if the target disk is populated, it seems to work OK (though of course you might hit https://bugzilla.redhat.com/show_bug.cgi?id=863348 later).

I attempted to install in a VM with f18b-smoke5 (anaconda-18.13-1) using an empty disk

When I selected the disk and attempted to use autopart, this traceback showed up.


Package: anaconda-18.13
OS Release: Fedora release 18

(In reply to comment #18)
> I believe this bug actually happens _only_ if the target disk is empty (no
> partitions, I guess is the definition of 'empty' here.) if the target disk
> is populated, it seems to work OK (though of course you might hit
> https://bugzilla.redhat.com/show_bug.cgi?id=863348 later).

I tried an install using f18b-smoke5 (anaconda-18.13-1) on a disk that had an old install of F18 on it. I hit https://bugzilla.redhat.com/show_bug.cgi?id=863593 which looks similar to my uneducated eyes but I could well be wrong.

well you hit it later, which is interesting. I did a test with a populated disk where I could get into the guided 'free up space' workflow and then it crashed when trying to remove partitions - but it crashed with 863348, not 863593. I also did a test with a populated disk and using *custom* partitioning, and that actually worked properly: I could remove the existing partitions and create new ones and complete the install, all successfully.

For Installation Destination, choose harddrive with GPT but no partitions.  Click Continue.

Package: anaconda-18.13
OS Release: Fedora release 18

*** Bug 863593 has been marked as a duplicate of this bug. ***

This is kinda hastily put together, but you can try:

updates=http://clumens.fedorapeople.org/13updates.img

And then I'll deal with really submitting patches next week.

*** Bug 863711 has been marked as a duplicate of this bug. ***

anaconda-18.14-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.14-1.fc18

Package anaconda-18.14-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.14-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-15707/anaconda-18.14-1.fc18
then log in and leave karma (feedback).

Discussed at 2012-10-10 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-10/f18beta-blocker-review-3.2012-10-10-16.05.log.txt . Accepted as a blocker per Alpha criterion "The installer must be able to complete an installation using automatic partitioning to any sufficiently large target disk, whether unformatted, empty, or containing any kind of existing data".

I can't reproduce the original bug with anaconda 18.12 and therefore I can't verify that it's fixed.

Steve, Tim, Adam, please try to reproduce with Beta TC4, thanks.

(In reply to comment #29)
> I can't reproduce the original bug with anaconda 18.12 and therefore I can't
> verify that it's fixed.
> 
> Steve, Tim, Adam, please try to reproduce with Beta TC4, thanks.

The reports are against 18.13 ...

I can still reproduce this with my test image that had 18.13, and I can't reproduce it in TC3 (which had 18.14) or TC4 (18.16), so we can close this (18.14 went stable).