Created attachment 841036 [details] image of the screen with error message Description of problem: I have tried several times to upgrade fedora 19 to 20 with fedup. fedup --network 20 with up-to-date fedora 19 (same results for 3.11 and 3.12 kernels) and fedup 0.8.0 finishes without any obvious errors. fedup log file shows no obvious errors. Version-Release number of selected component (if applicable): Linux xxx.xxx 3.12.5-200.fc19.x86_64 #1 SMP Tue Dec 17 22:21:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Installed Packages Name : fedup Arch : noarch Version : 0.8.0 Release : 3.fc19 Size : 237 k Repo : installed From repo : updates Summary : The Fedora Upgrade tool URL : https://github.com/wgwoods/fedup License : GPLv2+ Description : fedup is the Fedora Upgrade tool. How reproducible: Happens the same way each time I have tried it: 4 times so far. Steps to Reproduce: 1.fedup --network 20 2.reboot; choose "Fedora Upgrade" 3.boot hangs (see attached screen image) Actual results: The attached image shows the screen after booting from "Fedora Upgrade" option. The system will stay here indefinitely until a forced poweroff. Final screen message is: [ 9.042324] systemd[1]: Failed to initialize SELinux content: No such file or directory Booting again from a fedora 19 kernel is successful. Expected results: Should boot and continue the upgrade process. Additional info: System is a 2012 Dell XPS 14 laptop with Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz. This is not a UEFI system.
Other people report fedup working in general, so this might be something specific to your system. Can you try with selinux in non-enforcing mode? (Add 'permissive' at the end of the kernel command-line in the grub menu).
Thanks for the suggestion Zbigniew. I have tried both adding permissive to the kernel command line as suggested and also changing the selinux setting in /etc/selinux/config. The end result is still the same problem: failure to complete the boot process with the same error message
I was able to bypass the problem by adding selinux=0 to the fedup kernel boot command line. After that, the upgrade completed successfully and I am now running fedora 20.
selinux=0 is just a kludge.
(In reply to Aaron Dotter from comment #3) > I was able to bypass the problem by adding > > selinux=0 > > to the fedup kernel boot command line. After that, the upgrade completed > successfully and I am now running fedora 20. A libvirt VM hosted on Ubuntu 12.04 has the same problems. Selinux was not enabled. fedup version 0.8.0-3 Required: # Bug 1044086 - Fedup 19->20 fails rpmkeys --import /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-20-primary # Failed without selinux-policy-targeted yum install selinux-policy-targeted # and on kernel command line. selinux=0
"yum install selinux-policy-targeted" was enough for me to process. Without that, system cannot boot after rebooting.
*** Bug 1045182 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 1044484 ***