Bug 242047
| Summary: | Anaconda creates incorrect grub.conf when upgrading | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Simon Andrews <simon.andrews> | ||||||||||||
| Component: | anaconda | Assignee: | David Cantrell <dcantrell> | ||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||||||||||
| Severity: | low | Docs Contact: | |||||||||||||
| Priority: | low | ||||||||||||||
| Version: | 7 | CC: | bbaetz, bobgus, orion | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | All | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2007-10-23 00:08:07 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: |
|
||||||||||||||
|
Description
Simon Andrews
2007-06-01 13:30:13 UTC
Created attachment 155875 [details]
The grub.conf file created by anaconda during update to F7
See also bug 24043 Did you also have Raid and volume groups? See also bug 242043 (corrected from previous posting) Did you also have Raid and volume groups? No RAID or volume groups on my server. Once the F7 kernel was selected it all booted fine. That said the two bugs may be related. Having just updated another server the error seems to stem from the Grub config options in the update. Anaconda runs through the full set of options, including trying to detect other installations on the machine. At this point it seems to pick up the FC6 install which is about to be replaced and adds that as the default entry in the new grub file. By the time it comes round to being used the FC6 install has been upgraded and therefore won't boot. I'd suspect it's the invocation of the code to create a new grub.conf during an update rather than a fresh install which causes this. Anaconda needs to recognise the install which it's about to replace and not offer that as an additional grub line. *** Bug 242053 has been marked as a duplicate of this bug. *** Can you attach /var/log/anaconda.log and /root/upgrade.log? Created attachment 156120 [details] anaconda.log written at update time I hope you are reading the comments and fixes in the other related bug reports bug 241949 and bug 237415 Created attachment 156122 [details]
/root/upgrade.log
See above above request
See above comment
Created attachment 156448 [details]
Anaconda log (as requested)
Created attachment 156449 [details]
Upgrade log (as requested)
Adding a non-attachment comment to get this bug out of NEEDINFO (I've reported this bug before but it still seems to be broken!) Fixed this up for Fedora 8 *** This bug has been marked as a duplicate of 325871 *** |