Bug 529900
| Summary: | Counter-intuitive way to do network install using boot.iso | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michal Schmidt <mschmidt> | ||||||
| Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | rawhide | CC: | rvykydal, vanmeeuwen+fedora | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-10-23 09:39:41 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
If you use the boot.iso, you are getting a network install using the Fedora mirroring system by default. If you want to specify your own network source, you need to use the repo= parameter or the askmethod parameter in the boot arguments. (In reply to comment #1) > If you use the boot.iso, you are getting a network install using the Fedora > mirroring system by default. Chris, That's not what happened. I'd be very happy if Anaconda offered me the network install using the Fedora mirroring system. But it did not do that. It wrongly assumed I wanted to use an image on a local disk. Note that I have a wired LAN connection with DHCP, so Anaconda should have no trouble getting the mirrorlist. > If you want to specify your own network source, you need to use the repo= > parameter or the askmethod parameter in the boot arguments. I do not want to specify my own network source. I'd be satisfied if Anaconda used the default mirrors. Can you attach a screenshot of tty3 and tty4? Or, the complete /tmp/syslog and /tmp/anaconda.log files? Created attachment 365393 [details]
/tmp/syslog
/tmp/syslog from Anacoda
The interesting bits happen at time Oct 20 17:44:14 where Anaconda seems to have abandoned the hope that I could have a working network connection.
Created attachment 365394 [details]
/tmp/anaconda.log
The corresponding /tmp/anaconda.log. See the events at timestamp 17:44:17 here too.
I think the problem here is that boot.iso is copied to USB disk and so install.img (stage2) is not taken immediately from the boot.iso (as it would be from CDROM/DVD) as media is not detected in this case. Instead, stage2= boot option is taken into account. See https://bugzilla.redhat.com/show_bug.cgi?id=524417#c8 and https://bugzilla.redhat.com/show_bug.cgi?id=524417#c9. *** This bug has been marked as a duplicate of bug 528809 *** |
Description of problem: It is possible to install from network after booting from boot.iso, but the way to do it is counter-intuitive. Version-Release number of selected component (if applicable): Whatever is in F12-Beta (anaconda-12.38-1.fc12 I guess). How reproducible: always Steps to Reproduce: 1. Download boot.iso from F12-Beta and use dd to put it on a USB flash. 2. Boot from the USB flash. 3. Choose "Install or upgrade an existing system" in the boot menu 4. Accept default (English) in "Choose a Language" 5. Accept default (us) in "Keyboard Type" Actual results: You are now prompted to "Select Partition" where the installation image can be found. You are now confused because you want to install from network. Out of desperation you choose the "Back" button which does NOT take you back where you were before ("Keyboard Type"), but to the "Installation Method" screen where you can select "URL" as the installation source. Good, it is possible to install from network after all, but it was not obvious at all. Expected results: After selecting the keyboard type, the "Installation Method" screen should appear. And the Back button should never act like a secret passage to otherwise inaccessible screens.