| Summary: | upgrade fails during system upgrade FC19 > 20 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Joshua Cormney <rootedg33k> | ||||
| Component: | fedup | Assignee: | Will Woods <wwoods> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 21 | CC: | rootedg33k, tflink, udovdh, wwoods | ||||
| 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: | 2015-12-02 03:04:54 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: |
|
||||||
I found a work around for anyone having this issue, if you do a yum update before trying to run fedup I have found that it runs without a hitch. So the severity can be lowered. But it might be a good idea to include this near the begging of the fedup script just to avoid future bug reports. At the time of writing fedup-0.8.0-3.fc19.noarch is the latest. It did not work for me, unless I used the info from bug 1045847. So what issue was fixed in this bug? I have no issues with the grub entry. That seems to be a different issue all together. (In reply to Joshua Cormney from comment #3) > I have no issues with the grub entry. That seems to be a different issue all > together. OK, thanks. So this bug has a root cause that needs to be uncovered still? Technically yes. I found if I do a yum update before running the fedup command I don't run into the error I reported, but I would still say that for simplicity sake to include that as part of the fedup process. This way you reduce the number of users who try fedup once have it fail then give up. So to resolve the bug I would say simply adding the yum update command prior to prepping the packages would be advised. This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 20 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. This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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. |
Created attachment 839724 [details] SS of the error. Description of problem: fedup-cli --network 20 -v --debuglog fedup.log --nogpgcheck --reboot Will pull all the files fine and prep the system for upgrade but after the reboot once your in the system upgrade screen it fails out wiht the following error (Also ss attached.) "Cannot finalize remaining file systems and devices. giving up." Then reboots. Version-Release number of selected component (if applicable): fedup-0.8.0-3.fc19.noarch.rpm How reproducible: Every time. This was happening on two separate machines so its not just a one time occurrence. Dell T1650 Dell T1700 Steps to Reproduce: 1.fedup-cli --network 20 -v --debuglog fedup.log --nogpgcheck --reboot 2.watch the screen 3. Actual results: Reboots into the normal OS without an upgrade actually being preformed. Expected results: Upgraded to 20 from 19. Additional info: