Bug 1045721

Summary: fedup upgrade fails...
Product: [Fedora] Fedora Reporter: udo <udovdh>
Component: fedupAssignee: Will Woods <wwoods>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: sergio, tflink, wwoods
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: 2014-01-17 22:49:38 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:

Description udo 2013-12-21 13:15:36 UTC 
Description of problem:
Fedora 20 is released without fixing the important bugs in fedora 19.
So we receive plenty of bugzapper emails about Fedora 18 bugs.
Thus we are noticing the Fedora 20 release.
We run the `fedup-cli  --network 20` a few times, fixing issues as we go along.
Eventually just some gthumb dependency issue remains.
We decide to reboot.
At the first try the fedup upgrade kernel stops after complaining about selinux.
So we boot again with selinux=0 for this fedup upgrade kernel.
This time the boot does more.
After a while we see our known xwindows login.
We press ctrl-alt-F2 to see an open shell with a 'system-upgrade:#' prompt or similar with a message saying 'amibuous redirect' or similar before that.
We assume the upgrade has failed.
This far, since fedup was introduced and the upgrade option on the DVD vanished, we have been unable to use fedup successfully on three different systems with three different setups and this try was on the simplest setup.
So you may understand how we feel about this.

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

How reproducible:
See above.


Actual results:
No upgrade.

Expected results:
Upgraded Fedora.

Additional info:
As I explained before: why reboot twice for an update?
We have a running system that works.
So get to runlevel 1 and replace all binaries.
Only then reboot.

The other upgrade options (besides running fedup from the dvd or iso) is yum.
This indicates to me that you do not want to have people upgrade their Fedora's like they used to. (insert DVD, boot, select upgrade, have a drink)
You migth want to change that perception as it may not be present only with me.
Comment 1 udo 2013-12-22 08:58:56 UTC 
WARNING: potential problems with upgrade
  gthumb-3.2.5-1.fc19.x86_64 (no replacement) requires cogl-1.14.0-3.fc19.x86_64 (replaced by cogl-1.16.0-2.fc20.x86_64)
Comment 2 udo 2013-12-22 09:47:32 UTC 
Tried again.
Again 2000+ packages downloaded. (see the other bugs for optimizing there)
Result:
Boot into F19 with root shell on tty2 showing:

system-upgrade:/# mktemp: failed to create file via template '/tmp/.colorlsXXX': Read-only file system
bash: $TMP: ambiguous redirect
system-upgrade:/#

And nothing else there....
Comment 3 udo 2013-12-22 11:21:39 UTC 
FWIW:

This F19 x86_64 box has one HD that has an LVM thingie on there.
No raid.
No encryption except for swap.

Where can we find logs to see what went wrong?
Comment 4 Will Woods 2014-01-17 22:49:38 UTC 
The SELinux problem is filed as bug 1044484. Otherwise:

*** This bug has been marked as a duplicate of bug 1046347 ***