| Summary: | fedup fc19 to fc20 fails (VBox) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | thatdude | ||||||
| Component: | fedup-dracut | Assignee: | Will Woods <wwoods> | ||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 19 | CC: | mattwilmott, tflink, wwoods | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-02-17 19:42:05 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
thatdude
2013-12-17 22:07:33 UTC
Created attachment 838017 [details]
snapshot before shutdown
captured last screen just before shutting down (and rebooting back to fc19)
It still says 'Welcome to Fedora 19...' :-(
Created attachment 838025 [details]
snapshot of errors during 'System Upgrade' boot
Only these two lines are RED i.e. in [FAILED] state during 'System Upgrade'
[FAILED] Failed to mount Arbitrary Executable File Formats File System.
..but these are shown during the erroneous shutdown taking place instead of the expected System Upgrade
..then it successfully reboots back to fc19 (all log lines green)
Yeah I just had the same thing happen on a Dell Latitude E6520. Got all the way to the reboot, the default was the Fedora 20 Upgrade in Grub it executed and then rebooted me back to fedora 19 Ok stupid me, it appears I was using fedup version 0.7, retrieving the latest from updates-testing (0.8.x) and rerunning solved this issue. (In reply to Matt Wilmott from comment #4) > Ok stupid me, it appears I was using fedup version 0.7, retrieving the > latest from updates-testing (0.8.x) and rerunning solved this issue. Yes this worked for me too but then this guide needs fixing: http://docs.fedoraproject.org/en-US/Fedora/20/html/Installation_Guide/ch18s02.html # yum --enablerepo=updates-testing update fedup ---> Package fedup.noarch 0:0.7.3-4.fc19 will be updated ---> Package fedup.noarch 0:0.8.0-3.fc19 will be an update ...and it worked like a charm I would expect version 0.8.0-3 to be pushed to fc19's updates for people to upgrade flawlessly This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. |