Description of problem: Update from F19 to F20 fails: The boot image fails to complete with error message: systemd[1]: Failed to initialize SELinux context: Nu such file or directory Steps to Reproduce: 1. Install fed-up 2. Run fedup-cli --network 20 3. Select fedup boot option Additional info: SELinux is disabled on my system.
Same issue. Steps to Reproduce: (See above) Additional info: SELinux is disabled on my system, too. Upgraded to fedup 8 during earlier issue. ----- Given the reaction this 'selinux disabled' use case caused on the IRC channel #Fedora, perhaps making selinux==permissive/enabled an explicit requirement across the board for F21 would serve the user community's interests?
Perhaps, but it'd be even nicer if they could stick in an if-statement somewhere :D
https://bugzilla.redhat.com/show_bug.cgi?id=1044541
Just to confirm: the problem can be circumvented by setting selinux=permissive, rebooting and relabeling and re-running fedup, then setting selinux=disabled again once the upgrade is complete.
I just ran into this as well. FedUp should not fail when selinux is disabled.
I confirm the work-around. Setting SELinux to permissive/targeted allows fedup to run successfully. SUGGESTED TODO: Add test to ensure all supported Fedora/SELinux configurations are properly tested.
"yum install selinux-policy-targeted" is a possible workaround - I didn't have that package installed, and the server failed to boot into fedup. https://bugzilla.redhat.com/show_bug.cgi?id=1046191 is a duplicate of this bug.
*** Bug 1046191 has been marked as a duplicate of this bug. ***
I have the same problem. I get the same error message (systemd[1]: Failed to initialize SELinux context: No such file or directory). I have fedup-0.8.0-3.fc19.noarch I have tried to erase as many SELinux packages as possible, but I still have the following: $ rpm -qa | grep -i selinux libselinux-utils-2.1.13-15.fc19.i686 libselinux-python-2.1.13-15.fc19.i686 selinux-policy-3.12.1-74.14.fc19.noarch libselinux-2.1.13-15.fc19.i686 I have "SELINUX=disabled" in /etc/selinux/config When booting to Fedup, if I add the following to the boot command (the line starting linux...), then fedup will get past the SELinux error message: selinux=0 enforcing=0 I have had so many problems with SELinux in the past that I don't want to enable it any more.
*** Bug 1060595 has been marked as a duplicate of this bug. ***
The problem is this: When fedup reboots selinux is turned on by default. If it finds any files that do not have the proper selinux labels then the system will lockup. Usually what happens is that selinux was turned off and then files were written. The only cure that I found was to load the old system, turn selinux on and let it reformat all file labels. That solved the problem.
I've faced similar problem. Adding 'selinux=0 enforcing=0' to kernel boot options is a good workaround.
just a tip, to be able to use the system prior to fedup, editing /boot/grub.conf was useless, I had to edit /boot/extlinux/extlinux.conf btw, i am using a Fedora cloud image.
*** Bug 1084519 has been marked as a duplicate of this bug. ***
*** Bug 1084517 has been marked as a duplicate of this bug. ***
I'm not sure my issue was totally selinux. I do have selinux disabled, but fedup upon reboot, relabeled the system, rebooted, then just booted into the old system running with a F20 kernel though and that's it. Sifting around other bug reports (like https://bugzilla.redhat.com/show_bug.cgi?id=964303), I tried adding "systemd.unit=system-upgrade.target" to the grub boot line. This, and just that, allowed the continuation of the upgrade to completion.
(In reply to Zing from comment #16) > Sifting around other bug reports (like > https://bugzilla.redhat.com/show_bug.cgi?id=964303), I tried adding > "systemd.unit=system-upgrade.target" to the grub boot line. This, and just > that, allowed the continuation of the upgrade to completion. Do you have a separate /var partition? If so, you're hitting bug 1045168.
Hmmm. Yes, I have a /var partition... thanks, that must be it.
fedup 19 -> 20: I'm hitting this with SELINUX=permisssive
(In reply to sean darcy from comment #19) > fedup 19 -> 20: I'm hitting this with SELINUX=permisssive No, you aren't. If you have SELINUX=permissive then you have a different problem. This bug *only* concerns systems where /etc/selinux/config has SELINUX=disabled. The workaround for *this* bug is to put "selinux=0" in the boot options. (NOTE: Do *not* put "selinux=0" in the boot options unless your system has SELinux disabled!) On the other hand: * If you have a separate /var partition, install fedup-0.8.0-4 (currently in updates-testing). See bug 1045168 for details. * If you have multiple encrypted partitions, *sometimes* the upgrade won't start; Ctrl-Alt-Del should let you reboot and try again. You can also add "enforcing=0" to make this work. * If you have encrypted partitions *and* the bootloader config uses the old-style 'rd_LUKS_UUID=' option, see bug 1012899. * Otherwise... please file a new bug. But please, no more comments about unrelated problems. It just makes things more confusing.
OK, https://bugzilla.redhat.com/show_bug.cgi?id=1086431
*** Bug 1021228 has been marked as a duplicate of this bug. ***
Good night, I went to upgrade my Fedora 19 to 20 via Fedup, but it did not work ... Could someone give a hand in it ... In downloanding appeared some errors for the public key of the packages ... - Glee-5.4.0-5 *. - GitPython-0.3.2-0.6.RC1 * - Gconf2-3.2.6-7 * - Amule-nogui-2.3.1-4 * - Akmod-nvidia-304xx.304.183-1 * - Faad2-libs-2.7.5 * - Rpmfusion-nonfree-release-20-1 * And when I boot crashed on startup ... And the only thing indicating error appeared was this line [7.540807] systemd [1] faleid to initialize SELinux context: No such file or directory kind regards, Massao
fedup-dracut-0.9.0-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/fedup-dracut-0.9.0-1.fc21
Package fedup-dracut-0.9.0-1.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing fedup-dracut-0.9.0-1.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-13615/fedup-dracut-0.9.0-1.fc21 then log in and leave karma (feedback).
fedup-dracut-0.9.0-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.