Bug 1047074 - Fedup fails to upgrade FC19 -> FC20
Summary: Fedup fails to upgrade FC19 -> FC20
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-28 20:30 UTC by Michael Fratoni
Modified: 2015-06-29 13:53 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 13:53:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
upgrade log (249.53 KB, text/plain)
2013-12-28 20:30 UTC, Michael Fratoni
no flags Details
fedup.log (2.69 MB, text/plain)
2013-12-28 20:33 UTC, Michael Fratoni
no flags Details

Description Michael Fratoni 2013-12-28 20:30:15 UTC
Created attachment 842756 [details]
upgrade log

Description of problem:Fully updated FC19 system fails during package installation. Upon booting into system upgrade, update started in text mode. After installing 65% of new packages, the system rebooted leaving both FC19 and FC20 packages in place. I was able to salvage the system and update to FC20 by hand.
Relevant log lines appear below: (I have attached the fedup log and rdsosreport.txt)

[ 1982.879918] paradox.home upgrade[837]: [1414/1669] (65%) installing kstars-4.11.4-1.fc20...
[ 1985.396718] paradox.home kernel: traps: system-upgrade-[851] general protection ip:7f380fb0f07b sp:7fff3fc9e990 error:0 in libdb-5.3.so[7f380f9c4000+1b5000]
[ 1985.404456] paradox.home upgrade[837]: //lib/dracut/hooks/upgrade/50-do-upgrade.sh: line 4:   851 Segmentation fault      $UPGRADEBIN --root=/sysroot $args


Version-Release number of selected component (if applicable):fedup-0.8.0-3.fc20.noarch


How reproducible: Unknown


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: This is the 3rd failed attempt to update this machine with fedup. FC17 -> FC18 failed in a similar manner and was salvaged the same way. When FC18 -> FC19 also failed, I did a clean install hoping it would prevent another failure.

Comment 1 Michael Fratoni 2013-12-28 20:33:42 UTC
Created attachment 842757 [details]
fedup.log

Comment 2 Fedora End Of Life 2015-05-29 10:12:32 UTC
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.

Comment 3 Fedora End Of Life 2015-06-29 13:53:36 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.


Note You need to log in before you can comment on or make changes to this bug.