Bug 981180

Created attachment 768634 [details]
boot error after upgrade

Description of problem:
This is a follow-up of bug 798691. Anaconda no longer performs upgrades, but fedup does. I tried the same approach:

1. install F18 Live i686
2. insert F19 DVD x86_64 *by mistake*
3. run "fedup --device" and upgrade

180 packages were upgraded (I assume all noarch ones), the rest was left intact. The end result is a non-booting system due to:

"Failed to load SELinux policy. Freezing."

Providing selinux=0 helps to boot and the system seems at least basically functional (firefox and terminal works).

We should really guard our users from mistakes that can render their system non-functional, even though we might consider it "their fault". We need to increase our software's reliability.

How can fedup warn the user about possible problems? Ideas:
1. check whether --device contains the same architecture repository as is the installed system, and refuse to continue or at least print a big fat warning in that case
2. if there are any packages that wouldn't be upgraded using the chosen update method, print a warning a provide their list somewhere. If the number of not-to-be-upgraded packages is substantial when compared to installed packages, make the warning stronger.


Version-Release number of selected component (if applicable):
fedup-0.7.3-4.fc18

How reproducible:
always

Steps to Reproduce:
1. install F18 Live i686
2. insert F19 DVD x86_64 *by mistake*
3. run "fedup --device" and upgrade

Actual results:
upgrade is performed and system is rendered nonfunctional

Expected results:
upgrade is refused or the user is very clearly warned that something is wrong and what the outcomes may be