Bug 747920
| Summary: | Machine is unbootable after F15-F16 upgrade | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Need Real Name <lsof> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | anaconda-maint-list, awilliam, jonathan, lsof, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-21 16:30:35 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 713568 | ||
|
Description
Need Real Name
2011-10-21 11:58:44 UTC
Might be a problem with grubby. I don't know what writes the template that is missing. Which option did you choose at the bootloader upgrade screen: "new bootloader configuration" or "skip bootloader configuration"? Please attach the full logs. Those errors from grubby aren't actually necessarily as fatal as they seem (you get the same errors when you do a yum upgrade from f15 to f16 and then update the kernel, but grub config actually gets updated correctly). I didn't choose any bootloader option, it was an automated upgrade using preupgrade. Bug 741538 has logs from an install of another machine with the same problem. ah. if you used preupgrade then this is https://bugzilla.redhat.com/show_bug.cgi?id=737731 . There's now an updated F15 build of preupgrade: https://admin.fedoraproject.org/updates/preupgrade-1.1.10-1.fc15 which should have this fixed. Please re-test with that. *** This bug has been marked as a duplicate of bug 737731 *** |