Bug 1045182

Summary:	Upgrade to Fedora20 freezes, when selinux-policy-targeted not installed
Product:	[Fedora] Fedora	Reporter:	Tomas Lestach <tlestach>
Component:	fedup	Assignee:	Will Woods <wwoods>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	aaron.dotter, chupaka, tflink, tlestach, wwoods
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-08 18:02:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tomas Lestach 2013-12-19 19:49:54 UTC

Description of problem:
On one of my computer I have selinux disabled and selinux-policy-targeted package uninstalled. When I tried to upgrade F19 to F20 using fedup, the tool freezes.
Last message displayed:
systemd[1]: failed to initialize selinux context: no such file or directory

Version-Release number of selected component (if applicable):
latest fedup in Fedora19

How reproducible:
always

Steps to Reproduce:
1. disable selinux on Fedora19 and uninstall selinux-policy-targeted package
2. install fedup and try to upgrade using --network option to Fedora20

Actual results:
Fedup pre-downloads all the packages and after restart it freezes with:
systemd[1]: failed to initialize selinux context: no such file or directory

Expected results:
Successful upgrade to Fedora20

Comment 1 Aaron Dotter 2013-12-25 09:50:18 UTC

I submitted a bug report recently because I experience the same problem reported here despite the fact that, on my system, selinux-policy-targeted is installed.

https://bugzilla.redhat.com/show_bug.cgi?id=1046191

Comment 2 Will Woods 2014-01-07 20:03:20 UTC

Does your system have SELinux disabled?

Comment 3 Tomas Lestach 2014-01-08 07:47:57 UTC

(In reply to Will Woods from comment #2)
> Does your system have SELinux disabled?

Yes, it does.

Comment 4 Will Woods 2014-01-08 18:02:08 UTC

Then this is the same root cause as bug 1046191.

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