Bug 147302
| Summary: | Install update doesn't change boot loader config | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | jummie2k <jversteeg> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-02-07 15:45:04 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: | |||
If a kernel package isn't installed, then we don't have the information to actually create or update boot loader configuration. Isn't all the necessary information present in the already installed kernel package(s)? If I understand your comment correctly, the installer's "update" option does not apply to the boot loader at all: - If you update Fedora, boot loader is rewritten - If you don't and change the boot loader, you're screwed. So the only option is to completely reinstal. That's a pitty. Could you at least print a message in the installer's help? |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041020 Firefox/0.10.1 Description of problem: When using "update" (rather than install) to modify the boot loader configutration, the changes are not saved. Since update does not find kernel updates, it displays a message box reading something like "no kernel upgrades, boot loader configuration not changed". I think the boot loader configuration is not changed at all. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Download boot cd from ftp mirror (os/images/boot.iso) 2. Install but specify wrong boot loader location (MBR of /dev/hda instead of /dev/sda) 3. Reboot: boot loader is not started (Windows started here) 4. Reboot with install CD, select update 5. Modify boot loader location (MBR of /dev/sda) Actual Results: See step 3: boot loader configuration is not changed, Windows started up again. Expected Results: Boot loader should have been started. Additional info: I "fixed" it by reinstalling, this time using the correct boot loader config. I flagged this bug with i386 platform but I guess I could have selected "All". I haven't tested though so I didn't.