Bug 1044484 - Update from F19 to F20 fails: SELinux error when booting fedup image
Summary: Update from F19 to F20 fails: SELinux error when booting fedup image
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: 19
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1021228 1046191 1060595 1084517 1084519 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-18 12:17 UTC by Michael Clerx
Modified: 2014-10-28 21:48 UTC (History)
17 users (show)

Fixed In Version: fedup-dracut-0.9.0-1.fc21
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-28 21:48:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michael Clerx 2013-12-18 12:17:30 UTC
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.

Comment 1 Mike Lieman 2013-12-18 14:05:59 UTC
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?

Comment 2 Michael Clerx 2013-12-18 14:08:02 UTC
Perhaps, but it'd be even nicer if they could stick in an if-statement somewhere :D

Comment 4 Michael Clerx 2013-12-19 11:36:49 UTC
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.

Comment 5 Jonathan Kamens 2013-12-20 12:46:27 UTC
I just ran into this as well. FedUp should not fail when selinux is disabled.

Comment 6 Mike Lieman 2013-12-20 12:53:44 UTC
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.

Comment 7 Chupaka 2014-01-07 19:26:19 UTC
"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.

Comment 8 Will Woods 2014-01-13 17:59:55 UTC
*** Bug 1046191 has been marked as a duplicate of this bug. ***

Comment 9 Juhani Jaakola 2014-01-18 13:20:26 UTC
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.

Comment 10 Will Woods 2014-02-03 17:36:05 UTC
*** Bug 1060595 has been marked as a duplicate of this bug. ***

Comment 11 G.S. Link 2014-02-18 20:10:24 UTC
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.

Comment 12 vdm 2014-03-10 19:50:44 UTC
I've faced similar problem.
Adding 'selinux=0 enforcing=0' to kernel boot options is a good workaround.

Comment 13 javierwilson 2014-03-14 16:53:12 UTC
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.

Comment 14 Will Woods 2014-04-04 18:19:22 UTC
*** Bug 1084519 has been marked as a duplicate of this bug. ***

Comment 15 Will Woods 2014-04-04 18:19:57 UTC
*** Bug 1084517 has been marked as a duplicate of this bug. ***

Comment 16 Zing 2014-04-07 13:28:47 UTC
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.

Comment 17 Will Woods 2014-04-07 13:43:44 UTC
(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.

Comment 18 Zing 2014-04-08 12:55:43 UTC
Hmmm. Yes, I have a /var partition... thanks, that must be it.

Comment 19 sean darcy 2014-04-09 20:41:39 UTC
fedup 19 -> 20: I'm hitting this with SELINUX=permisssive

Comment 20 Will Woods 2014-04-09 21:12:14 UTC
(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.

Comment 21 sean darcy 2014-04-10 21:30:55 UTC
OK, https://bugzilla.redhat.com/show_bug.cgi?id=1086431

Comment 22 Will Woods 2014-04-25 19:20:30 UTC
*** Bug 1021228 has been marked as a duplicate of this bug. ***

Comment 23 Massao 2014-07-19 02:31:19 UTC
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

Comment 24 Fedora Update System 2014-10-23 18:06:46 UTC
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

Comment 25 Fedora Update System 2014-10-27 08:16:48 UTC
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).

Comment 26 Fedora Update System 2014-10-28 21:48:53 UTC
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.


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