Hide Forgot
Description of problem: If Fedora 18 Beta is used in a PXE boot configuration where inst.repo=nfs points to a directory containing both the Fedora .iso and LiveOS, an "Unknown error" dialog appears at graphical installer start that prevents installation. This structure is used to enable HTTP installs in addition to NFS. This structure works with previous Fedora releases. Version-Release number of selected component (if applicable): Anaconda 18.29.2 How reproducible: Steps to Reproduce: 1. Place LiveOS/squashfs.img in the same directory as Fedora-18-Beta-i386-DVD.iso. 2. Launch a PXE boot using inst.repo=nfs:server:/path/to/iso/ 3. On graphical installer start, "An unknown error has occurred" appears. Actual results: The installer is prevented from installing. Expected results: The installer should use the .iso and ignore the LiveOS directory when passing inst.repo=nfs. Additional info: Fedora ├── 17 │ └── 32bit │ ├── Fedora-17-i386-DVD.iso │ ├── Fedora-17-i386-DVD.torrent │ └── LiveOS │ └── squashfs.img ├── 18 │ └── 32bit │ ├── Fedora-18-Beta-i386-DVD.iso │ ├── Fedora-18-Beta-i386-DVD.torrent │ └── LiveOS │ └── squashfs.img LABEL fedora17-32bit-http MENU LABEL Install Fedora 17 - 32-bit (HTTP) KERNEL images/fedora/17/32bit/vmlinuz APPEND initrd=images/fedora/17/32bit/initrd.img inst.repo=http://192.168.2.100/dist/iso/Fedora/17/32bit LABEL fedora17-32bit-nfs MENU LABEL Install Fedora 17 - 32-bit (NFS) KERNEL images/fedora/17/32bit/vmlinuz APPEND initrd=images/fedora/17/32bit/initrd.img inst.repo=nfs:192.168.2.100:/srv/dist/iso/Fedora/17/32bit LABEL fedora18-32bit-http MENU LABEL Install Fedora 18 Beta - 32-bit (HTTP) KERNEL images/fedora/18/32bit/vmlinuz APPEND initrd=images/fedora/18/32bit/initrd.img inst.repo=http://192.168.2.100/dist/iso/Fedora/18/32bit LABEL fedora18-32bit-nfs MENU LABEL Install Fedora 18 Beta - 32-bit (NFS) KERNEL images/fedora/18/32bit/vmlinuz APPEND initrd=images/fedora/18/32bit/initrd.img inst.repo=nfs:192.168.2.100:/srv/dist/iso/Fedora/18/32bit
Can you attach /tmp/anaconda.log and /tmp/packaging.log to this bug report? Thanks.
Updating with logs from Fedora 18 release (instead of Beta). I get: The installer has tried to mount the installation image, but cannot find it on the hard drive. / Should I try again to locate the image? If I click "No" there is a brief pause before I get the "Unknown error" dialog again.
Created attachment 704065 [details] anaconda log
Created attachment 704066 [details] packaging log
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.