Bug 1046191 - boot fails after fedup f19 to f20 (SELinux disabled/uninstalled)
Summary: boot fails after fedup f19 to f20 (SELinux disabled/uninstalled)
Keywords:
Status: CLOSED DUPLICATE of bug 1044484
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 20
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1045182 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-24 02:56 UTC by Aaron Dotter
Modified: 2014-01-13 17:59 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-13 17:59:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
image of the screen with error message (607.61 KB, image/jpeg)
2013-12-24 02:56 UTC, Aaron Dotter
no flags Details

Description Aaron Dotter 2013-12-24 02:56:08 UTC
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.

Comment 1 Zbigniew Jędrzejewski-Szmek 2013-12-24 04:45:08 UTC
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).

Comment 2 Aaron Dotter 2013-12-25 09:52:55 UTC
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

Comment 3 Aaron Dotter 2013-12-26 01:48:21 UTC
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.

Comment 4 Zbigniew Jędrzejewski-Szmek 2013-12-26 02:56:12 UTC
selinux=0 is just a kludge.

Comment 5 Rick Foos 2014-01-04 00:35:15 UTC
(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

Comment 6 Chupaka 2014-01-07 19:23:04 UTC
"yum install selinux-policy-targeted" was enough for me to process. Without that, system cannot boot after rebooting.

Comment 7 Will Woods 2014-01-08 18:02:08 UTC
*** Bug 1045182 has been marked as a duplicate of this bug. ***

Comment 8 Will Woods 2014-01-13 17:59:55 UTC

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


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